Yes, it's still working. There's a message in the terminal "SET: not found" but it is not keeping it from running! - Just seen, apparently another option would be using the cross-env package that we have already installed in the dev dependencies (would then become a regular dependency). So that would work across different OS: "cross-env NODE_ENV=production node index.js" Can somebody test on Windows? Anyway, thanks for fixing it @ArchDD!