search

blueimp / atom-open-terminal-here

Open the Terminal (Mac OS X, Linux) or Command Prompt (Windows) in the given directory via context menu or keyboard shortcut in the Atom text editor.
https://atom.io/packages/open-terminal-here
MIT License
47 stars 20 forks source link

NODE_ENV is set to production #7

Closed jscissr closed 8 years ago

jscissr commented 8 years ago

When I open cmd using this tool, the NODE_ENV environment variable is automatically set to production, which is not what I want.

The terminal currently inherits all the environment vars set by Atom. This makes the it less usable for node development.

jscissr commented 8 years ago

This is the same issue as karan/atom-terminal#74

blueimp commented 8 years ago

Thanks for the report @jscissr. I've included your fix suggested in the atom-terminal issue as part of the default command on Windows.

Unfortunately this is a general issue with environment variables leaking from the parent process on the Windows platform, as explained in this Stack Overflow post.