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
env values in npm.start not handled correctly #615
Comments
... Between what versions? On Sat, 22 Aug 2015 04:44 Operations Research Engineering +Software <
|
let me check |
this problems started happening about 2 weeks ago, so if there was a recent version change that was it. And it happens for me on both Windows and Mac OSX.
|
if you look in the above dump, somehow nodemon is turning this:
into this
this is dreadful, I cannot use nodemon and I need it! like I said this problem is occuring on both Windows and Mac... |
I hope I am not right, but it looks like something is really wrong right now with your lib |
that dump was from OSX, but in the screenshot at the very top, the same exact thing happens on Windows |
Something must have changed with the nodemon module itself since my same package.json settings suddenly began to error out, as you can see from this command:
looks like in your library you are setting the NODE_ENV variable the unix way, but that doesn't work on windows, you need to use
set NODE_ENV=
The text was updated successfully, but these errors were encountered: