1. Home
  2. Tags
  3. npm

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!

Log in to post
  • ?

    Are there plans to support AuthToken authentication to the NPM feeds?

    Support proget npm authentication
    2
    0 Votes
    2 Posts
    42 Views
    ?
    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 npm proget
    2
    0 Votes
    2 Posts
    11 Views
    ?
    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 authentication npm
    4
    0 Votes
    4 Posts
    18 Views
    ?
    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 npm proget
    8
    0 Votes
    8 Posts
    28 Views
    ?
    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
    16
    0 Votes
    16 Posts
    71 Views
    ?
    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. [image: 0285.tools-options2_15477577.png] 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 npm proget documentation
    7
    0 Votes
    7 Posts
    18 Views
    ?
    Thanks!!!!!! That will help a lot.
  • ?

    Npm packages give 404 not found

    Support proget npm packages
    2
    0 Votes
    2 Posts
    19 Views
    ?
    Found the problem: It was an incorrect credentials at the connector.
  • ?

    NPM and Windows Authentication

    Support npm proget
    18
    0 Votes
    18 Posts
    221 Views
    M
    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
    2
    0 Votes
    2 Posts
    4 Views
    ?
    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
    3
    0 Votes
    3 Posts
    11 Views
    F
    That did the trick! Thanks for the hint.
  • ?

    Log in - npm commandline

    Support authentication proget npm
    4
    0 Votes
    4 Posts
    40 Views
    ?
    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
    8
    0 Votes
    8 Posts
    33 Views
    ?
    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 authentication installation ldap proget npm
    3
    0 Votes
    3 Posts
    48 Views
    ?
    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 npm proget
    4
    0 Votes
    4 Posts
    17 Views
    ?
    Looks like reinstall helped. Thank you!
  • ?

    NPM connector do not download scoped packages

    Support npm proget
    2
    0 Votes
    2 Posts
    14 Views
    ?
    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
    4
    0 Votes
    4 Posts
    4 Views
    ?
    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

    Locked Support proget iis npm
    9
    0 Votes
    9 Posts
    22 Views
    E
    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 feeds npm proget
    2
    0 Votes
    2 Posts
    9 Views
    ?
    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
    2
    0 Votes
    2 Posts
    8 Views
    ?
    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 packages npm proget
    3
    0 Votes
    3 Posts
    24 Views
    ?
    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