Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    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!

    Multiple npm feeds

    Scheduled Pinned Locked Moved Support
    proget
    4 Posts 1 Posters 5 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      Are multiple npm feeds supported in ProGet?

      I added two npm feeds. Running 'npm search' and 'npm publish' against either of them (command line) would give error:

      "MultipleNpmFeeds The client is using the wrong search URL, and there are multiple
      npm feeds available, so ProGet cannot determine which feed to search.: -/all"
      

      If I remove one, leaving only one npm feed, then npm search/publish would work.

      Does ProGet support only one npm feed? or am I missing some configuration somewhere? Thanks.

      Product: ProGet
      Version: 3.4.7

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        ProGet supports multiple npm repository... but currently, there is a bug in the npm client's search command, where it ignores everything in repository URL after the host name.

        If you only have one npm repository, ProGet can work around npm's bug by searching the single repository... but otherwise, npm client isn't saying which repository to use. Hence the error.

        There are a lot of search problems with the npm client right now... check out npm-kludge-search for a replacement that mostly works.

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          Thanks Alana.

          Does your comment about the npm search bug apply to npm publish as well? We're seeing the error with npm publish as well. Aside from limiting ourselves to only one npm feed, is there a workaround (for command line publish)?

          1 Reply Last reply Reply Quote 0
          • ? This user is from outside of this forum
            Guest
            last edited by

            I believe the publish bug was fixed in the latest npm; you may want to update.

            Or, maybe it was broken in the latest npm (v2.5.0). In that case, you will want to downgrade.

            I believe we tested last against v2.2.0.

            I would also suggest to post this on the npm issue tracker, as will help raise the priority/importance of fixing and maintaining tests to work with repositories other than npmjs.org -

            1 Reply Last reply Reply Quote 0

            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

            With your input, this post could be even better 💗

            Register Login
            • 1 / 1
            • First post
              Last post
            Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation