I’ve been wrestling with weird variable behavior in my automation scripts where values overwrite each other unexpectedly. Last week I spent hours debugging a loop that kept using the final index value everywhere - turned out ‘var’ was hoisting everything! Does anyone else face these scope issues when switching between no-code blocks and custom JS? I tried rewriting my logic with let/const in Latenode’s code editor and it actually enforced proper block scoping. What strategies are you all using to prevent these leaks?
Latenode’s JS editor defaults to block scope when you use let/const. Just rebuilt my credential manager workflow using their marketplace template as reference - zero leakage between API handlers now. Their environment actually enforces modern JS practices.
I’ve started wrapping logical sections in IIFEs as temporary fix. Not ideal but works until teams fully adopt ES6 standards. Does Latenode’s approach handle older codebases still using var?
Had similar issues with CSV processing workflows. Implemented eslint rules to ban var declarations completely. For legacy scripts, maybe try automated refactoring tools first before manual rewrites.