-
Notifications
You must be signed in to change notification settings - Fork 321
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
nodePath not working (vscode-tslint) #179
Comments
Environment Info:OS: Windows 7 |
I have been trying to assemble a test case to illustrate the problem, but unfortunately there isn't any test coverage for the |
Closed
dbaeumer
added a commit
that referenced
this issue
Mar 7, 2017
I fixed this on the server to correctly handling the path comparison. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
You can read the original issues description in vscode-tslint #173.
Whenever I try to set a
nodePath
for vscode-tslint, it always ends up using the global node_modules path.You can see that even though the NODE_PATH has a value, it still continues on to call
resolveGlobalNodePath
.From
server/src/files.ts
:The text was updated successfully, but these errors were encountered: