Hi,
I'm using VS 2015 preview 1 with NTVS RC 1. I am using a private npm repository (npm Enterprise, see: https://docs.npmjs.com/enterprise/intro) which allows me to install @scoped packages which are private to me. Note, this is using npm.exe v2.1.18 to allow use of @scoped packages. The projects I mention below are written in TypeScript.
I am seeing odd behaviour from the integrated npm tooling where it shows packages listed within the 'global' scope incorrectly:
Issue 1:
The item underneath the global list displays: "@myScope@0.0.0 (not listed in package.json)". In my package.json I have @myScope/somePackage defined as a devDependecy which the built-in tooling correctly lists, so:
- Where is this entry underneath the global scope coming from?
- Why is it listed with a completely incorrectname?
Issue 2:
In another project (this is the 2nd of 2 projects within the solution) I'm seeing a similar issue but in this case I am seeing 'packageName@0.0.0' where packageName should actually be '@myScope/packageName@1.2.3'.
- The @myScope part of the package name is completely missing from the listing in the globals list.
- The version number associated with the package is wrong, with it being stated as 0.0.0 instead of 1.2.3.
With both of issues my computer is grinding to a halt because there are 4 'npm-cli.js ls -g' processes burning all of my resources. Is there a way I can turn off the built-in npm tooling while still reaping the benefits of JavaScript intellisense? I'm happy to use the command line or Node interactive window to drive npm behaviour manually.
Is the use of the @ symbol to identify a package scope causing an issue? With @scoped packages coming to the public npm repository soon (http://blog.npmjs.org/post/100099402720/registry-roadmap) this is certainly going to be a frequent way to reference packages.
I'm using VS 2015 preview 1 with NTVS RC 1. I am using a private npm repository (npm Enterprise, see: https://docs.npmjs.com/enterprise/intro) which allows me to install @scoped packages which are private to me. Note, this is using npm.exe v2.1.18 to allow use of @scoped packages. The projects I mention below are written in TypeScript.
I am seeing odd behaviour from the integrated npm tooling where it shows packages listed within the 'global' scope incorrectly:
Issue 1:
The item underneath the global list displays: "@myScope@0.0.0 (not listed in package.json)". In my package.json I have @myScope/somePackage defined as a devDependecy which the built-in tooling correctly lists, so:
- Where is this entry underneath the global scope coming from?
- Why is it listed with a completely incorrectname?
Issue 2:
In another project (this is the 2nd of 2 projects within the solution) I'm seeing a similar issue but in this case I am seeing 'packageName@0.0.0' where packageName should actually be '@myScope/packageName@1.2.3'.
- The @myScope part of the package name is completely missing from the listing in the globals list.
- The version number associated with the package is wrong, with it being stated as 0.0.0 instead of 1.2.3.
With both of issues my computer is grinding to a halt because there are 4 'npm-cli.js ls -g' processes burning all of my resources. Is there a way I can turn off the built-in npm tooling while still reaping the benefits of JavaScript intellisense? I'm happy to use the command line or Node interactive window to drive npm behaviour manually.
Is the use of the @ symbol to identify a package scope causing an issue? With @scoped packages coming to the public npm repository soon (http://blog.npmjs.org/post/100099402720/registry-roadmap) this is certainly going to be a frequent way to reference packages.