Topics tagged under "npm" | Inedo Community Forums

Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

?

Are there plans to support AuthToken authentication to the NPM feeds?
Support • proget npm authentication • 31 Jan 2017, 13:37 • Don Harper 1 Feb 2017, 02:14

2

0
Votes

2
Posts

41
Views

? 1 Feb 2017, 02:14

Auth tokens are now supported for npm feeds; you'll need to create the token as a ProGet API Key. Please see the API & Access Key documentation to learn more. This is an updated answer; earlier the answer mentioned the feature was not supported.
?

Bulk import NPM packages
Support • proget npm • 21 Dec 2016, 15:56 • Don Harper 21 Dec 2016, 17:56

2

0
Votes

2
Posts

11
Views

? 21 Dec 2016, 17:56

You can just drop your npm packages in the configured drop folder; they need to be valid npm package,s which means <name>-<version>.tgz file format.
?

On IIS: npm adduser fails on server with a NotSupportedException: The given path's format is not supported.
Support • proget npm authentication • 8 Dec 2016, 07:35 • Don Harper 13 Dec 2016, 11:46

4

0
Votes

4
Posts

18
Views

? 13 Dec 2016, 11:46

It looks like there was a regression in 4.6.0 that is causing this change in behavior. We'll have it fixed in ProGet 4.6.3, which will should be released by tomorrow at the latest.
?

Private npm Modules
Support • proget npm • 30 Nov 2016, 11:17 • Don Harper 2 Dec 2016, 13:48

8

0
Votes

8
Posts

27
Views

? 2 Dec 2016, 13:48

I see; have you've tried putting in your npmjs username and password in the connector? If that doesn't work, then it's not a supported scenario.
?

Npm scoped packages - String is not a valid semantic version error
Support • proget npm connectors • 14 Nov 2016, 22:32 • Don Harper 30 Mar 2017, 08:19

16

0
Votes

16
Posts

71
Views

? 30 Mar 2017, 08:19

I found this thread after experiencing a similar issue. I was seeing the "string is not a valid semantic version error" from Proget when npm would try to install scoped packages, but only when the npm install was automatically triggered inside Visual Studio by a change to the package.json. We already had the latest version of Proget with the change to the web.config and installs worked fine when running from command line. Problem turned out to be the fact that Visual Studio 2015 had installed it's own copy of the npm.cmd as an external web tool. This was an older version than the one I had installed globally, but the order of external web tool locations in Visual Studio had the path to the older version listed before my system path. Making system path take precedence solved the issue. Just thought I'd post this here in case anyone else with a similar issue stumbles across this thread like I did.
?

Improve Markdown Style?
Support • proget npm documentation • 10 Nov 2016, 20:34 • Don Harper 2 Dec 2016, 12:17

7

0
Votes

7
Posts

18
Views

? 2 Dec 2016, 12:17

Thanks!!!!!! That will help a lot.
?

Npm packages give 404 not found
Support • proget npm packages • 8 Nov 2016, 13:41 • Don Harper 17 Nov 2016, 09:29

2

0
Votes

2
Posts

19
Views

? 17 Nov 2016, 09:29

Found the problem: It was an incorrect credentials at the connector.
?

NPM and Windows Authentication
Support • proget npm • 8 Nov 2016, 11:39 • Don Harper 18 Apr 2018, 03:36

18

0
Votes

18
Posts

220
Views

M 18 Apr 2018, 03:36

I've managed to get this working in v5.0.11 by setting up the second ProGet website in IIS with anonymous authentication enabled and pointing to the same physical path as the original website. The same AppPool is shared between the two and is using the Integrated pipeline. No other IIS or .config configuration was required. In ProGet, for the npm feed that required anonymous access I added the Anonymous user to the feed permissions under Administration > Security > Users & Tasks. Restarting the web services then enabled the anonymous access to the feed using the second website's bindings.
?

Export all version of npm package
Support • proget npm • 8 Nov 2016, 04:11 • Don Harper 8 Nov 2016, 08:20

2

0
Votes

2
Posts

4
Views

? 8 Nov 2016, 08:20

You may have luck grabbing the packages from the internal, disk-based package store, and copying those to the drop path on the new server.
F

Npm registry not working?
Support • proget npm • 4 Nov 2016, 09:10 • florian.peschka_9815 4 Nov 2016, 09:20

3

0
Votes

3
Posts

11
Views

F 4 Nov 2016, 09:20

That did the trick! Thanks for the hint.
?

Log in - npm commandline
Support • proget npm authentication • 24 Oct 2016, 13:21 • Don Harper 25 Oct 2016, 09:32

4

0
Votes

4
Posts

40
Views

? 25 Oct 2016, 09:32

The URL must still be incorrect; the /npm endpoints will return JSON-based content, where as the errors shown is HTML-based body content (<!DOCTYPE html>...). You can use a tool like Fiddler to see precisely what URLs are being requested, and then hopefully diagnose/trace from there.
?

Does ProGet support npm dist-tag or tag?
Support • proget npm • 19 Oct 2016, 00:19 • Don Harper 23 Feb 2017, 16:40

8

0
Votes

8
Posts

32
Views

? 23 Feb 2017, 16:40

I see. It appears that dist-tag rm is now failing. We'll investigate and if we are able to reproduce this then it should be easy enough to get in the next maintenance release.
?

Publishing NPM packages
Support • proget npm authentication installation ldap • 17 Oct 2016, 10:52 • Don Harper 19 Oct 2016, 10:40

3

0
Votes

3
Posts

48
Views

? 19 Oct 2016, 10:40

Hi Christian, the information you posted had mentioned internal packages (Aeon Framework, etc), so I removed it That said, it wasn't an error message, but a JSON document that contained metadata information about packages. This is an expected response if you visit an API URL directly in your browser, and when the npm client relies on the JSON data. If you are receiving an error from the npm client, please make sure to share: the precise error message that npm client is using the precise URL that the npm client is requesting; you can get this by running Fiddler, and seeing the requests that the client makes Note that you will need to disable Windows Integrated Authentication at the IIS level, not just within ProGet.
?

NPM publish issue
Support • proget npm • 5 Oct 2016, 10:44 • Don Harper 6 Oct 2016, 06:12

4

0
Votes

4
Posts

17
Views

? 6 Oct 2016, 06:12

Looks like reinstall helped. Thank you!
?

NPM connector do not download scoped packages
Support • proget npm • 4 Oct 2016, 05:47 • Don Harper 4 Oct 2016, 09:45

2

0
Votes

2
Posts

14
Views

? 4 Oct 2016, 09:45

This is a limitation of npm unfortunately; scoped packages are not included in the npmjs.org index, therefore there is no way to search for a scoped package via a connector. However if you already know the name, then it will work, and can be retrieved from the connector.
?

Typings
Support • proget npm • 28 Sept 2016, 12:36 • Don Harper 12 Oct 2016, 15:37

4

0
Votes

4
Posts

4
Views

? 12 Oct 2016, 15:37

Well if you used "npm" as a source, and then set up that as a registry in ProGet, then it could be a source.
?

NPM - RAM consumption 5GB
Support • proget npm iis • 9 Sept 2016, 07:36 • Don Harper 11 Dec 2024, 10:00

9

0
Votes

9
Posts

22
Views

E 11 Dec 2024, 10:00

we experience mem usage on fresh filling of cache (20gb) with npm connector attached to a feed. once the cache is filled with all the dependencies usage is down to 2gb.
?

NPM Feed Issue
Support • proget npm feeds • 17 Aug 2016, 06:22 • Don Harper 17 Aug 2016, 09:14

2

0
Votes

2
Posts

9
Views

? 17 Aug 2016, 09:14

Hi Junaid, This is a known issue with npm; basically it's sending a JSON document with two "dist" properties. For example... { "dist": "value1", ..., "dist": "value2" } The JSON Library we're using isn't too keen on that, and we already have a fixe (PG-603) planned/scheduled for the next release.
?

How exactly does the License filter work?
Support • proget npm licensing • 29 Jul 2016, 09:59 • Don Harper 4 Aug 2016, 09:49

2

0
Votes

2
Posts

8
Views

? 4 Aug 2016, 09:49

Currently, only NuGet feeds use the license filter, it shouldn't be displayed on npm feeds... We do plan on adding support for better licensing filtering in a future version, as the current implemention is a bit limiting.
S

NPM feed and dependencies
Support • proget npm packages • 27 Jun 2016, 11:32 • stijn.peeters.external_8202 28 Jun 2016, 09:24

3

0
Votes

3
Posts

24
Views

? 28 Jun 2016, 09:24

angular-cli gave me problems. It tries to retrieve dependent packages from https://registry.npmjs.org. ( https urls don't works on our dev pc's) At the moment I also configured the server with the feed as my proxy server, so at least that traffic passes over this server for all package handling. (I also have github and such) Tnx for any info you can provide Stijn

3 / 5

Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation

Are there plans to support AuthToken authentication to the NPM feeds? Support • proget npm authentication • 31 Jan 2017, 13:37 • Don Harper 1 Feb 2017, 02:14

Bulk import NPM packages Support • proget npm • 21 Dec 2016, 15:56 • Don Harper 21 Dec 2016, 17:56

On IIS: npm adduser fails on server with a NotSupportedException: The given path's format is not supported. Support • proget npm authentication • 8 Dec 2016, 07:35 • Don Harper 13 Dec 2016, 11:46

Private npm Modules Support • proget npm • 30 Nov 2016, 11:17 • Don Harper 2 Dec 2016, 13:48

Npm scoped packages - String is not a valid semantic version error Support • proget npm connectors • 14 Nov 2016, 22:32 • Don Harper 30 Mar 2017, 08:19

Improve Markdown Style? Support • proget npm documentation • 10 Nov 2016, 20:34 • Don Harper 2 Dec 2016, 12:17

Npm packages give 404 not found Support • proget npm packages • 8 Nov 2016, 13:41 • Don Harper 17 Nov 2016, 09:29

NPM and Windows Authentication Support • proget npm • 8 Nov 2016, 11:39 • Don Harper 18 Apr 2018, 03:36

Export all version of npm package Support • proget npm • 8 Nov 2016, 04:11 • Don Harper 8 Nov 2016, 08:20

Npm registry not working? Support • proget npm • 4 Nov 2016, 09:10 • florian.peschka_9815 4 Nov 2016, 09:20

Log in - npm commandline Support • proget npm authentication • 24 Oct 2016, 13:21 • Don Harper 25 Oct 2016, 09:32

Does ProGet support npm dist-tag or tag? Support • proget npm • 19 Oct 2016, 00:19 • Don Harper 23 Feb 2017, 16:40

Publishing NPM packages Support • proget npm authentication installation ldap • 17 Oct 2016, 10:52 • Don Harper 19 Oct 2016, 10:40

NPM publish issue Support • proget npm • 5 Oct 2016, 10:44 • Don Harper 6 Oct 2016, 06:12

NPM connector do not download scoped packages Support • proget npm • 4 Oct 2016, 05:47 • Don Harper 4 Oct 2016, 09:45

Typings Support • proget npm • 28 Sept 2016, 12:36 • Don Harper 12 Oct 2016, 15:37

NPM - RAM consumption 5GB Support • proget npm iis • 9 Sept 2016, 07:36 • Don Harper 11 Dec 2024, 10:00

NPM Feed Issue Support • proget npm feeds • 17 Aug 2016, 06:22 • Don Harper 17 Aug 2016, 09:14

How exactly does the License filter work? Support • proget npm licensing • 29 Jul 2016, 09:59 • Don Harper 4 Aug 2016, 09:49

NPM feed and dependencies Support • proget npm packages • 27 Jun 2016, 11:32 • stijn.peeters.external_8202 28 Jun 2016, 09:24

Are there plans to support AuthToken authentication to the NPM feeds?
Support • proget npm authentication • 31 Jan 2017, 13:37 • Don Harper 1 Feb 2017, 02:14

Bulk import NPM packages
Support • proget npm • 21 Dec 2016, 15:56 • Don Harper 21 Dec 2016, 17:56

On IIS: npm adduser fails on server with a NotSupportedException: The given path's format is not supported.
Support • proget npm authentication • 8 Dec 2016, 07:35 • Don Harper 13 Dec 2016, 11:46

Private npm Modules
Support • proget npm • 30 Nov 2016, 11:17 • Don Harper 2 Dec 2016, 13:48

Npm scoped packages - String is not a valid semantic version error
Support • proget npm connectors • 14 Nov 2016, 22:32 • Don Harper 30 Mar 2017, 08:19

Improve Markdown Style?
Support • proget npm documentation • 10 Nov 2016, 20:34 • Don Harper 2 Dec 2016, 12:17

Npm packages give 404 not found
Support • proget npm packages • 8 Nov 2016, 13:41 • Don Harper 17 Nov 2016, 09:29

NPM and Windows Authentication
Support • proget npm • 8 Nov 2016, 11:39 • Don Harper 18 Apr 2018, 03:36

Export all version of npm package
Support • proget npm • 8 Nov 2016, 04:11 • Don Harper 8 Nov 2016, 08:20

Npm registry not working?
Support • proget npm • 4 Nov 2016, 09:10 • florian.peschka_9815 4 Nov 2016, 09:20

Log in - npm commandline
Support • proget npm authentication • 24 Oct 2016, 13:21 • Don Harper 25 Oct 2016, 09:32

Does ProGet support npm dist-tag or tag?
Support • proget npm • 19 Oct 2016, 00:19 • Don Harper 23 Feb 2017, 16:40

Publishing NPM packages
Support • proget npm authentication installation ldap • 17 Oct 2016, 10:52 • Don Harper 19 Oct 2016, 10:40

NPM publish issue
Support • proget npm • 5 Oct 2016, 10:44 • Don Harper 6 Oct 2016, 06:12

NPM connector do not download scoped packages
Support • proget npm • 4 Oct 2016, 05:47 • Don Harper 4 Oct 2016, 09:45

Typings
Support • proget npm • 28 Sept 2016, 12:36 • Don Harper 12 Oct 2016, 15:37

NPM - RAM consumption 5GB
Support • proget npm iis • 9 Sept 2016, 07:36 • Don Harper 11 Dec 2024, 10:00

NPM Feed Issue
Support • proget npm feeds • 17 Aug 2016, 06:22 • Don Harper 17 Aug 2016, 09:14

How exactly does the License filter work?
Support • proget npm licensing • 29 Jul 2016, 09:59 • Don Harper 4 Aug 2016, 09:49

NPM feed and dependencies
Support • proget npm packages • 27 Jun 2016, 11:32 • stijn.peeters.external_8202 28 Jun 2016, 09:24