Skip to content
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

"npm run test" is not recognized as an internal or external command #28928

Closed
drguildo opened this issue Jun 17, 2017 · 3 comments
Closed

"npm run test" is not recognized as an internal or external command #28928

drguildo opened this issue Jun 17, 2017 · 3 comments
Assignees

Comments

@drguildo
Copy link

  • VSCode Version: Code 1.13.1 (379d2ef, 2017-06-14T18:21:47.485Z)
  • OS Version: Windows_NT ia32 6.1.7601
  • Extensions:
Extension Author Version
html-snippets abusaidm 0.1.0
vscode-javascript-snippet-pack akamud 0.1.5
vscode-theme-onedark akamud 2.0.2
path-intellisense christian-kohler 1.4.2
jshint dbaeumer 0.10.15
vscode-eslint dbaeumer 1.2.11
monokai-plusplus dcasella 1.6.0
python donjayamanne 0.6.5
gitlens eamodio 4.1.2
vscode-npm-script eg2 0.2.0
auto-close-tag formulahendry 0.4.2
beautify HookyQR 1.1.1
vscode-icon-theme jtlowe 1.5.0
vscode-colorize kamikillerto 0.5.1
PowerShell ms-vscode 1.3.2
live-server-preview negokaz 0.0.4
red red-auto 0.2.1
java redhat 0.6.0
vscode-wakatime WakaTime 1.1.12

Steps to Reproduce:

  1. Alt + Shift + R
  2. Select npm: run test

Instead of getting npm output I get:

'"npm run test"' is not recognized as an internal or external command, operable program or batch file.

Both npm and node are in my path. I've tried putting npm in both my user path and system path and neither worked. If I open an integrated terminal, I can run npm run test as expected.

@ramya-rao-a ramya-rao-a added the tasks Task system issues label Jun 17, 2017
@dbaeumer dbaeumer assigned egamma and unassigned dbaeumer Jun 19, 2017
@dbaeumer dbaeumer removed the tasks Task system issues label Jun 19, 2017
@dbaeumer
Copy link
Member

dbaeumer commented Jun 19, 2017

@egamma Looks like this is caused by vscode-npm-script.

@egamma
Copy link
Member

egamma commented Jun 22, 2017

@dbaeumer agreed, moving the issue.

@egamma
Copy link
Member

egamma commented Jun 22, 2017

This issue was moved to microsoft/vscode-npm-scripts#39

@egamma egamma closed this as completed Jun 22, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
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

4 participants