BUG: Faulty Javascript being implemented in the Code node after update to v0.222.3

[shrey-42]

Describe the problem/error/question

Yesterday, i upgraded from v0.219.1 to latest (v0.222.3)
Since then, one workflow (checked so far) is erroring out in the code node, in a simple JS operation.

Please share your workflow

Example of the code in question:

Share the output returned by the last node

I checked in MDN to see whether the hasOwnProperty function has been deprecated. But that’s not the case either (Object.prototype.hasOwnProperty() - JavaScript | MDN).

As seen in the screenshot:

• Line 6 shouldn’t have executed at all

---

(Correct) Output as seen in v0.219.1 :

---

It’s rather troubling that basic JS is breaking down.

Information on your n8n setup

• n8n version: latest (0.222.3)
• Database (default: SQLite): Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main): main
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system: Ubuntu

[jonflow]

What’s the error?

Did you mean to check for the update property twice?

[shrey-42]

Updated:

@shrey-42

As seen in the screenshot:

• Line 6 shouldn’t have executed at all

---

[shrey-42]

Found already reported, related bug:

Checking for value in Webhook Body with hasOwnProperty

I am having an odd issue after updating to 0.222.1 last night. I get a JSON payload from the webhook that sometimes will have a key called “remove” with the value set to “yes”. The value is always yes if the remove key is in the JSON. I then set a variable in my code node that checks to see if that property exists in the Webhook payload, like this: let remove = $node["Webhook"].json["body"]["0"].hasOwnProperty("remove"); I then use a switch to set a variable named “state”, like this: cas…

[Jon]

This is N8N-6333 internally buddy.

[shrey-42]

Hi all.

@Jon

This is N8N-6333

Has there been any update on this, in any of the subsequent versions?

Thanks

[shrey-42]

I checked again with the release v0.226.0.

Same: faulty output.

[netroy]

@shrey-42 Thanks for reporting the issue, and also for including the test workflow; it was very helpful for debugging.

This is being addressed in PR 6124 , and will hopefully be included in the next release.

[jan]

New version [email protected] got released which includes the GitHub PR 6124.