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
  • ?

    Problem authentication (404) with NPM Feed

    Support authentication proget npm
    5
    0 Votes
    5 Posts
    35 Views
    ?
    Ah, I see. We have been able to reproduce this - it looks like a regression in handling the feed-specific npm adduser URL. We've also always handled the /siteroot/-/... one as well because npm used to always use that regardless of the repository URL. I think that changed some time around npm 2.7 when we added the second handler. Regardless, we've already fixed this internally (again), and will be releasing the fix as part of ProGet 3.8.1 likely some time tomorrow. Thanks for the help!
  • ?

    NPM Feed not caching remote private remote repositories

    Support proget npm
    3
    0 Votes
    3 Posts
    7 Views
    ?
    This issue has been resolved in ProGet 3.8.1.
  • ?

    Npm adduser fails with 404

    Support proget npm
    6
    0 Votes
    6 Posts
    42 Views
    ?
    npm changes its access URLs a lot, and from looking through its checkin history it usually seems to be accidental. ProGet currently supports two URLs for adduser: /-/user/org.couchdb.user or /npm/[FEED]/-/user/org.couchdb.user[...] I've never seen any version of npm use a ~ instead of a - before... What version did you upgrade from?
  • ?

    Proget with npm feed use massive a amounts of CPU/RAM

    Support proget npm
    4
    0 Votes
    4 Posts
    14 Views
    ?
    We have not had other users report this problem, nor have we seen it during testing. You can try running the service interactively (just stop the WIndows Service, then run the .exe file), and see what happens. Also worth noting, make sure that all the errors in the log are deleted before the packages start indexing again.