-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'NODE_ENV' is not recognized as an internal or external command, operable program or batch file. Windows #8
Comments
@nosizejosh would you mind testing this module to see if it works for you (with the original script command)? |
@JKHeadley which module? |
@nosizejosh sorry, forgot to link it: |
saw this while trying to troubleshoot, knew it would work but didn't want to just fix without reporting, also my fix was actually to place it as dependency in packages.json |
trying to create a pull request with below but its too much to clone the whole repo just for this small change. Adding the win-node-env does work as I suspected. I however added as a dependency instead of install globally.
|
Lol it's been like six years but if anyone is still stuck on this check this link |
the back-end will not run on Windows, after following all the steps due to the error
only way to get back-end to run is to edit the script source in package.json to
as explained here
The text was updated successfully, but these errors were encountered: