Hey @fgnass (and contributors), great ongoing work. We've been using node-dev for several years now and it's been awesome.
We just updated after a long time, and we hit the same issue with node-dev now setting NODE_ENV that @gasi did in #62 (comment).
It sounded like you agreed that node-dev should just not set NODE_ENV at all, since the caller who's calling node-dev can always set any environment variable they want. (Put another way, NODE_ENV=development doesn't tell you you're running in node-dev, so it's not serving that purpose. Instead, it's just assuming that code wants to set NODE_ENV by default, and to development.)
If that's still the case, I wanted to open this issue to capture this request. Would be great to have node-dev no longer set NODE_ENV! Thanks for your consideration. =)
Hey @fgnass (and contributors), great ongoing work. We've been using node-dev for several years now and it's been awesome.
We just updated after a long time, and we hit the same issue with node-dev now setting
NODE_ENVthat @gasi did in #62 (comment).It sounded like you agreed that node-dev should just not set
NODE_ENVat all, since the caller who's callingnode-devcan always set any environment variable they want. (Put another way,NODE_ENV=developmentdoesn't tell you you're running in node-dev, so it's not serving that purpose. Instead, it's just assuming that code wants to setNODE_ENVby default, and todevelopment.)If that's still the case, I wanted to open this issue to capture this request. Would be great to have node-dev no longer set
NODE_ENV! Thanks for your consideration. =)