Behaviour:
When I add a new dependency to the 'dependencies' node in the package.json I get the 'not installed' warning. [correct]
When I add that same dependency to the 'devDependencies' node I do not get the warning. [not correct]
When I add the dependency to both the 'dependencies' & 'devDependencies' node. I get a warning but only for the one in the 'devDependencies' node. [semi correct]

Expected behaviour:
I always get a warning when I add a new dependency to the package.json.
If I add a dependency to both nodes I expect 2 warnings.

please i am using vscode, i tried to install vscode by using

npm install, it said
bash code not found

Please, have a look at this issue: microsoft/vscode#21666

From @tyrsius on March 1, 2017 23:19

• VSCode Version: Version 1.10.0 (1.10.0)
• OS Version: macOS Sierre 10.12 (16A323)

Steps to Reproduce:

1. Create an empty project with the following package.json file

{
  "name": "vscode-bug",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "dependencies": {
    "engine-handlebars": "^0.8.0",
    "express": "^4.14.0",
    "newrelic": "^1.36.2",
    "node-uuid": "^1.4.7"
  },
  "devDependencies": {
    "autoprefixer-stylus": "^0.11.0",
    "babel-core": "^6.3.21",
    "babel-eslint": "^7.0.0",
    "babel-loader": "^6.2.0",
    "babel-plugin-transform-runtime": "^6.15.0",
    "babel-plugin-webpack-alias": "^2.1.1",
    "babel-preset-es2015": "^6.3.13",
    "babel-preset-react": "^6.3.13",
    "babel-preset-stage-0": "^6.3.13",
    "babel-tape-runner": "^2.0.1",
    "blue-tape": "^1.0.0",
    "chokidar-cli": "^1.2.0",
    "deep-extend": "^0.4.1",
    "immutable": "^3.8.1",
    "json-loader": "^0.5.4",
    "localforage": "^1.4.3",
    "npm-run-all": "^4.0.1",
    "qs": "^6.3.0",
    "raw-loader": "^0.5.1",
    "react": "^15.3.2",
    "react-addons-test-utils": "^15.3.2",
    "react-document-title": "^2.0.2",
    "react-dom": "^15.3.2",
    "react-hot-loader": "^3.0.0-beta.6",
    "react-markdown": "^2.4.2",
    "react-redux": "^4.4.5",
    "react-router": "^2.8.1",
    "react-router-redux": "^4.0.6",
    "redbox-react": "^1.3.2",
    "redux": "^3.6.0",
    "redux-thunk": "^2.1.0",
    "skin-deep": "^0.16.0",
    "snazzy": "^5.0.0",
    "source-map-loader": "^0.1.5",
    "standard": "^8.4.0",
    "stylus": "^0.54.5",
    "tap-spec": "^4.1.1",
    "url-join": "^1.1.0",
    "webpack": "^1.11.0",
    "webpack-dev-server": "^1.10.1"
  },
  "author": "",
  "license": "ISC"
}

2. run npm install
3. You will see the following problems listed for dependencies

[npm] Module 'https-proxy-agent' is extraneous
[npm] Module 'node-pre-gyp' is extraneous
[npm] Module 'readable-stream' is extraneous

These packages are not dependencies of the package, and this error should not show.

Copied from original issue: microsoft/vscode#21666

When I run > npm from vscode as a task, then use > npm: Terminate, the output message:
Killing process npm start (pid: xxxx)

And it's stuck forever, the task is never killed, until I restart vscode. This has been happening for a very long time (over a year). My current vscode version:

Version 1.20.0-insider
Commit b36655544f413f67aec02d64ce619d165749b957
Date 2018-01-15T05:14:00.163Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

there is pnpm / npminstall and others ..

plz add a config to npm

// https://github.com/Microsoft/vscode-npm-scripts/blob/master/src/main.ts#L192
let cmd = 'npm ' + args.join(' ');

Hello,
I have installed the npm package in Visual Studio Code. I need to run
'npm install -g jslint' because of errors.
But how can I run this command within Visual Studio Code?
thanks
regards
hawk

The root of the project isn't the place where my package.json is stored. That is stored in src/<project_name>.

I tried including that directory in npm.includeDirectories, but it doesn't want to perform an npm install from that directory. If I do not disable npm.useRootDirectory, it just performs the npm install twice in the root of my project.

If I set npm.useRootDirectory = false, then it only performs the npm install from the root of project, once.

"npm.includeDirectories": [
    "src/HTML5-front-end"
],
"npm.useRootDirectory": false

Also, does includeDirectories support the use of variables like ${workspaceRoot} ?

When I run with the configuration above,the following error is shown:

enoent ENOENT: no such file or directory, open '<root_path>/package.json', the <root_path> is actually the path to the root of my project, but I would think it would append the directory included in the configuration.

I have npm.runInTerminal set to false so the output goes to OUTPUT pane inside Visual Studio Code editor. I'm running a watching + server script with npm script extension. How do I stop the server now?

Can I specify which package.json file to use? I have an app within my app that has its own package.json file with its own npm scripts. Is there a way that could run those instead of the main ones?

I have some scripts in my package.json with a space in the name. I don't want to use "-" or "_" between words because i have a user-friendly GUI that reads these strings.
Can you add support for this?
Example:

"scripts": {
    "Install on server": "rm -r node_modules & npm install"
}

Error: npm ERR! missing script: Install

I have a workspace that contains 3 interdependent projects that all need to be npm started. If I use this extension to start them (via npm:Start -> All... or even individually instead of "all") they all attempt to run in the same terminal sequentially (I have "Run In Terminal" option selected). The problem is that they are all long-running server tasks, so it'll only actually run the first one. I need a way to have these all run in separate terminal processes at the same time. I'd also prefer if they were done using the "Split Terminal" function so I can watch all 3 at once, but if they all launch in their own terminal tab, that's fine too. I don't know if you want to make this a configuration setting or just one of the options to pop up in the command palette as you try to run it.

It conflicts with New File and makes New File a chording key binding

I got error whenever I open my package.json in the editor:
Finding installed modules failed SyntaxError: Unexpected end of JSON input

When disabled your extension error disappeared.

AFAIK, vsc autodetect npm scripts ("Tasks: run task" > select npm script). I would like to disable this extension (especially since it's duplication npm.runSilent setting) but I would like to keep using dependencies validation. Would it be possible to split the features into two extensions?

From @drguildo on June 17, 2017 10:13

• VSCode Version: Code 1.13.1 (379d2efb5539b09112c793d3d9a413017d736f89, 2017-06-14T18:21:47.485Z)
• OS Version: Windows_NT ia32 6.1.7601
• Extensions:

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.

Copied from original issue: microsoft/vscode#28928

I'm new to vscode, but I use a lot of npm scripts in my projects and this is a great plugin!

I'm having trouble with one thing though -- I have a couple of watch type tasks (e.g. using watchify). I'm having trouble killing those tasks through vscode. Selecting Tasks: Terminate Running Task doesn't seem to kill any npm script I start using this plugin. Is there another way to end these tasks?

Would be nice if this extension would respect breakpoints set in the npm script being run.

Much like we have Build and Test, I believe adding start would be helpful

The integrated terminal (in insider build) is already much better than the output window because it supports ANSi colors. It would be great if this could start tasks in the integrated terminal, instead of starting a new console or using the output window.

Migrating from original location

• VSCode Version: Version 1.10.0 (1.10.0)
• OS Version: macOS Sierre 10.12 (16A323)

Steps to Reproduce:

1. Create an empty project with the following package.json file

{
  "name": "vscode-bug",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "dependencies": {
    "engine-handlebars": "^0.8.0",
    "express": "^4.14.0",
    "newrelic": "^1.36.2",
    "node-uuid": "^1.4.7"
  },
  "devDependencies": {
    "autoprefixer-stylus": "^0.11.0",
    "babel-core": "^6.3.21",
    "babel-eslint": "^7.0.0",
    "babel-loader": "^6.2.0",
    "babel-plugin-transform-runtime": "^6.15.0",
    "babel-plugin-webpack-alias": "^2.1.1",
    "babel-preset-es2015": "^6.3.13",
    "babel-preset-react": "^6.3.13",
    "babel-preset-stage-0": "^6.3.13",
    "babel-tape-runner": "^2.0.1",
    "blue-tape": "^1.0.0",
    "chokidar-cli": "^1.2.0",
    "deep-extend": "^0.4.1",
    "immutable": "^3.8.1",
    "json-loader": "^0.5.4",
    "localforage": "^1.4.3",
    "npm-run-all": "^4.0.1",
    "qs": "^6.3.0",
    "raw-loader": "^0.5.1",
    "react": "^15.3.2",
    "react-addons-test-utils": "^15.3.2",
    "react-document-title": "^2.0.2",
    "react-dom": "^15.3.2",
    "react-hot-loader": "^3.0.0-beta.6",
    "react-markdown": "^2.4.2",
    "react-redux": "^4.4.5",
    "react-router": "^2.8.1",
    "react-router-redux": "^4.0.6",
    "redbox-react": "^1.3.2",
    "redux": "^3.6.0",
    "redux-thunk": "^2.1.0",
    "skin-deep": "^0.16.0",
    "snazzy": "^5.0.0",
    "source-map-loader": "^0.1.5",
    "standard": "^8.4.0",
    "stylus": "^0.54.5",
    "tap-spec": "^4.1.1",
    "url-join": "^1.1.0",
    "webpack": "^1.11.0",
    "webpack-dev-server": "^1.10.1"
  },
  "author": "",
  "license": "ISC"
}

2. run npm install
3. You will see the following problems listed for dependencies

[npm] Module 'https-proxy-agent' is extraneous
[npm] Module 'node-pre-gyp' is extraneous
[npm] Module 'readable-stream' is extraneous

These packages are not dependencies of the package, and this error should not show.

The install process is too long to capture in a gif. However, as you can see from this screenshot of the terminal, the only thing in this folder before I ran yarn was the package.json file, no node_modules folder. After installing, you can see the problems for extraneous packages.

Is there a guide to get this plugin to work with monorepos such as lerna? Is it possible?

Thank you!

What does it mean? Can someone explain please?

This repo has within it one of the best package.json validation scripts. It would be amazing if we can pull that specific code out and into it's own function, and then it's own CLI tool.

Ctrl+R is now assigned to Open recent in VS Code. Installing this extension disables the Open Recent. Can we change the shortcuts to something else?

Is there a way to run npm commands in the integrated terminal on visual studio?

I'm using git bash terminal in VS Code on Windows.
When I run scripts, plugin try cd me to root path.

`$ cd c:\Users\bogdan.lubenets\Documents\pos-app

bash: cd: c:Usersbogdan.lubenetsDocumentspos-app: No such file or directory`

vscode-npm-script 0.1.8, Windows 8, git bash

Hi there,
Is it possible right now or in a future to add a keybind to run a specific npm run?
So let's say I have a serve npm script thats runs a webserver,
I want to be able to make a shorcut let's say CTRL+ALT+S that would do something like this as command npm-script.run serve

When I'm running any command repeatedly the latest beginning of output is hard to identify.

Release notes for recent vscode update say:

We also now allow extensions to contribute tasks to the Run Task Quick Pick list programmatically. This opens VS Code up for use cases where an extension wants to add support for a specific build system and wants to contribute corresponding tasks. An example is the npm extension that can now contribute scripts defined in the package.json as tasks to VS Code programmatically.

Would love to see it being actually implemented!

Currently I have to wait a few seconds after saving the package.json before I get feedback from the validation process. I would be nice if the validation reports warnings as soon as I save the package.json or (if at all possible) while I am editing the file.

Would it be valuable or useful to be able to initialize a package.json via the Command Palette: > npm: init?

I'm looking for a way to run some npm scripts in Visual Studio Code (to lint/build/etc), then run, say, jasmine in debug mode from VSCode.

Currently to debug my tests, I have to:

npm run build_stuff
jasmine

I'd like to run the npm run build_stuff out of debug mode, then debug jasmine, which is running specs in my project.

Is it the intent of this extension to help support that use case?

when using bash on windows as vscode terminal
"terminal.integrated.shell.windows": "C:\\WINDOWS\\Sysnative\\bash.exe",

the vscode itself found the right path for project working on ,
but npm extension failed with the cd path (npm is working as well)
since working path is already the right one, so npm install will work

$ cd "d:\\Ricki\\Desktop\\vuelearn\\Vue2-MV"
cd: no such file or directory: d:\Ricki\Desktop\vuelearn\Vue2-MV
<ctrl+c>
$ pwd
/mnt/d/Ricki/Desktop/vuelearn/Vue2-MV
$ npm -v
3.10.10

Hello,

I run NPM script with this extension and then I close npm terminal which is integrated after running script and I can't launch anymore NPM script with this extension, need to do Reload Window or close VS Code.

To reproduce simple run NPM command which will be alive forever. Close it in your terminal by Kill Terminal and try to run NPM command with this extension, you can't.

I have following scripts defined in my package.json

"scripts": {
    "validate": "npm-run-all --parallel validate-webpack:* lint",
    "validate-webpack:dev": "webpack-validator webpack.config.js --env.dev",
    "validate-webpack:prod": "webpack-validator webpack.config.js --env.prod",
    "start": "webpack-dev-server --history-api-fallback --env.dev",
    "build": "webpack -w --env.dev",
    "test": "karma start",
    "clean-dist": "rimraf dist",
    "copy-files": "cpy \"**/index.html\" favicon.ico \"../dist\" --cwd=src --parents",
    "clean-and-copy": "npm run clean-dist && npm run copy-files",
    "prebuild": "npm run clean-and-copy",
    "prebuild:prod": "npm run clean-and-copy",
    "build:prod": "webpack --env.prod",
    "lint": "tslint -c tslint.json src/**/*.ts"
  }

but i see only build, install , test when i do ctrl + p and type npm.

any guess why it's behaving like this or it suppose to behave like this?

i'm usinng ubuntu 14.04

Hello here is the link I am following

https://dzone.com/articles/angular-2-and-spring-boot-development-environment

when I check with cmd prompt npm -v i am getting the below error.

'CALL "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" prefix -g' is not recognized as an internal or external command,
operable program or batch file.
5.5.1

How to get rid of this error.

I am able to see the nodejs in system variables.

Becuase of that I am not able to install angular cli

Hello,

please add support to run multiple npm scripts, because right now I can run only 1 script.

When I disable this extension the Intellisense in launch.json works as expected. When this extension is enabled only local previous values are presented in the Intellisense suggestion fold out.

Extension disabled:

Extension enabled:

In my use-case, my repo is lerna monorepo, where all my NPM packages are under the /packages folder, and each have their own package.json. The root also has a package.json

I can currently define "npm.includeDirectories" with an exhaustive list of all packages, but it gets painful to maintain, especially with 20+ packages:

	"npm.includeDirectories": [
		"packages/module1",
		"packages/module2",
		"packages/module3",
		"packages/module4",
		"packages/module5",
		"packages/module6",
		"packages/module7",
		"packages/module8",
               ...etc
	],

What I would like to do, is use a glob to match all packages inside the packages folder, which will include any new packages automatically:

"npm.includeDirectories": [
    "packages/*"
],

Feature request

When using the command palette to run npm scripts, they are alphabetized. OFten we run the same 1 or 2 repeatedly. It would be nice if the most frequently run script appeared first (once VS Code has seen them a few times). Kind of like how the most recently used files show up

• Extension Name: vscode-npm-script
• Extension Version: 0.3.5
• OS Version: Windows_NT x64 10.0.14393
• VSCode version: 1.28.0

We have written the needed data into your clipboard. Please paste:```json
{
"activationTimes": {
"startup": false,
"codeLoadingTime": 1681,
"activateCallTime": 44,
"activateResolvedTime": 0,
"activationEvent": "onLanguage:json"
}
}