I posted this bug a few months ago and had no replies. I am just wondering, should I expect it would ever be fixed? This is pretty significant. https://jpsoft.com/forums/threads/s...d-commands-doesnt-work-with-npm-scripts.7009/ To summarize, in some circumstances, exit codes returned by a process invoked inside a script are not passed on when the script itself exits. This makes any kind of chained process unreliable, e.g. later scripts may execute even though a prior script failed. Since a great many npm packages depend on this kind of functionality for ensuring prerequites to building, testing, and so on succeed, it makes TCC/LE difficult to use with npm and node. But generally, this could affect anything that uses && to chain scripts. I created a git repo to demonstrate the problem: https://github.com/jamietre/tccle-issue The readme shows how to reproduce the problem. The scripts work as expected using normal DOS CMD and bash shells.