Skip to content
This repository has been archived by the owner on Jul 2, 2020. It is now read-only.

Force NODE_PATH environment variable #1

Closed
jagged3dge opened this issue Oct 11, 2015 · 4 comments
Closed

Force NODE_PATH environment variable #1

jagged3dge opened this issue Oct 11, 2015 · 4 comments

Comments

@jagged3dge
Copy link

Is it possible to do force NODE_PATH from atom's exports folder to a different folder?

I've tried using:
NODE_PATH="D:\WebDevTools\nodejs,D:\npm-modules\node_modules"
but it seems it gets rejected and NODE_PATH in the opened terminal still shows:
NODE_PATH=C:\Users\Gary\AppData\Local\atom\app-1.0.19\resources\app.asar\exports

@jagged3dge
Copy link
Author

I just researched a little more and found a related issue reported to Atom editor repo: atom/atom#3311

@tkw1536
Copy link
Owner

tkw1536 commented Nov 19, 2015

@jagged3dge Where did you try changing the environment variable?

screen shot 2015-11-19 at 19 48 38

If you change the environmentVariables setting of this package to NODE_PATH=D:\WebDevTools\nodejs,ATOMERNIAL_FILE=$file,ATOMERNIAL_DIRECTORY=$directory,NODE_ENV= at least atoms value should be overriden. Unfortunatly you can not set environment variables to anything containing a comma right now.

@tkw1536
Copy link
Owner

tkw1536 commented Sep 4, 2017

This issue hasn't had any activity for a long time, closing.

@tkw1536 tkw1536 closed this as completed Sep 4, 2017
@jagged3dge
Copy link
Author

Oops, did not realize this issue was still open. I've since moved on to VSCode as my editor, ditching Atom.
Regardless, thank you for your package and continued support 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants