-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
Could not install typings files for JavaScript language features. Please ensure that NPM is installed or configure 'typescript.npm' in your user settings (again) #36444
Comments
Not sure if it's relevant, but attempting to execute the TypeScript compiler as a Task also fails. {
"compilerOptions": {
"target": "es6",
"module": "commonjs",
"sourceMap": true
}
} Running this from Tasks=>Run Build Task... results in:
In regular (bash shell) in integrated terminal:
I feel like there's a step I've missed somewhere to tell VSC to use the Linux subsystem rather than Windows. |
@dbaeumer should know more about the task issue. For the npm problem, I'm not sure if we properly support running npm inside of wsl. @andy-ms shuld be able to clarify that. To help investigate, can you you try:
This log file may help us understand what is going wrong |
OK.. this looks relevant:
|
Hmm.. Presumably the |
This is a know issue in when trying to run task in WSL. The problem is that we currently assume that if the OS is Windows, paths are Windows paths. This is not true when tasks are executed in WSL or in git bash. Besides the I can't comment on the typings issue but I think that the tsserver installs them on the Windows machine and not inside the WSL. |
Thank @dbaeumer! Yes for the typings they would be installed on the windows machine. @jasonpolites have you tried installing npm on windows and just pointing |
@dbaeumer Yeah fair enough. I thought with WSL I could see myself going back to Windows for dev work, but still being tethered to the Windows environment is a little awkward (for me). I predict various compatibility issues as NPM (etc) versions differ between Win and WSL and keeping them in sync is a bit of a pain. FWIW in Windows it would be amazing if VSC just had a |
@jasonpolites we are currently collecting WSL issues (we have a label for it) to decide what the best solution for the problem will be. |
ack. Feel free to close this if it keeps things clean. I'll assume my issue gets dragged into a broader set of wsl issues. Thanks for taking the time |
Ok, I'm going to close this as a duplicate of #20220 then For now, you'll still need to install npm in your windows environment to get automatic typings acquisition. Again though, you still should be able to still use your wsl npm for actually managing the project |
As per issue #24961 I'm creating a new issue with the same symptoms.
Environment
I access Node and NPM via NVM, then via the Integrated Terminal in VSC:
I've tried various flavors of
"typescript.npm"
including:No dice
I'd really like to stay within the Linux system rather than straddling the both Windows
PATH
and the subsystemPATH
The text was updated successfully, but these errors were encountered: