No matter what, You’ll always get a 401 for the feed. npmrc or service connection also brought up nothing. Verifying you don’t have legacy URLs (like ) in your. npmAuthenticate, npm login, npm config set registry, npm –registry, or any other weird trick won’t work. You want to access it from a project in another organization. You have an npm feed in your company’s Azure DevOps organization. That said, let’s take a step back from the void – what was the problem, again? Problem What I’m saying is that you need to be prepared for me to have completely forgotten everything about the topic whenever the post comes out. The latter depends on how many typos, misspellings, unnecessary repetition, and irrelevant/incoherent rambling requires fixing. Well, “just figured out” when writing this, not as of publishing the piece. This surprisingly painful piece of configuration was something I just figured out for a customer project, where the pipeline I was configuring depended on a number of packages in an “internal” npm feed, that was (unfortunately) published by an internal Team Project in another Azure DevOps organization – still owned and maintained by our customer. Ah – that’s when you know it’s going to be good, right? When someone goes as far as to throw away the Npm and NpmAuthenticate, and even “npm -install –registry”, because none of them worked, we’re getting to seriously desperate levels of irregularity. So, instead of the built-in ways to access npm feeds, this solution includes some PowerShell. Ah, well – life would be extremely boring if everything always went according to documentation, right? “You” being “me”, and the “edge case” being our internal npm feed (registry), for whatever reason. 4 min read.Īnother one in the series of “this should’ve been easy, but alas, you’re the edge case”. This post was most recently updated on January 14th, 2022.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |