Synchronized commands chaining for npm scripts

[bogdan-rosianu]

Type

• Bug
• Feature
• Refactoring
• Performance improvement

Problem setting

• commands chaining was not working every time because & makes the commands run asynchronously and in most cases the commands were dependent on the previous command's success

Proposed Changes

• use && instead of & because it will only continue with the next command AFTER the first command's exit code is 0 (successful)

Example

sleep 10 & print "test"

that will print 'test' asynchronously

vs

sleep 10 && print "test"

that will wait 10 seconds and only after that it will print 'test'