![npm start does not work on Windows: 'cross-env' is not recognized as an internal or external command · Issue #510 · saleor/saleor-storefront · GitHub npm start does not work on Windows: 'cross-env' is not recognized as an internal or external command · Issue #510 · saleor/saleor-storefront · GitHub](https://user-images.githubusercontent.com/12252472/71094475-51940200-21ab-11ea-8da5-ab7d48e8379b.png)
npm start does not work on Windows: 'cross-env' is not recognized as an internal or external command · Issue #510 · saleor/saleor-storefront · GitHub
![node.js - Nodejs actions testing via Github not working, because Dialect needs to be explicitly supplied - Stack Overflow node.js - Nodejs actions testing via Github not working, because Dialect needs to be explicitly supplied - Stack Overflow](https://i.stack.imgur.com/EuJ5s.png)
node.js - Nodejs actions testing via Github not working, because Dialect needs to be explicitly supplied - Stack Overflow
run npm script with cross-env and && not working properly · Issue #176 · kentcdodds/cross-env · GitHub
![node.js - Can't run "npm run prod" using a deploy.sh file in a Laravel project (using Laravel Mix) - Stack Overflow node.js - Can't run "npm run prod" using a deploy.sh file in a Laravel project (using Laravel Mix) - Stack Overflow](https://i.stack.imgur.com/5ldLu.jpg)
node.js - Can't run "npm run prod" using a deploy.sh file in a Laravel project (using Laravel Mix) - Stack Overflow
![React/Gatsby starter deployment error on run build: "Failed during stage 'building site': build script returned non-zero exit code: 137" - Support - Netlify Support Forums React/Gatsby starter deployment error on run build: "Failed during stage 'building site': build script returned non-zero exit code: 137" - Support - Netlify Support Forums](https://global.discourse-cdn.com/netlify/original/3X/b/f/bf1e204c84135e9e03a701e1bcf6421f8e014b2d.png)