Azure devops 如何使用纱线注册作为Azure DevOps工件上游馈送？

我在Azure DevOps中有一个包含JavaScript包的mono repo。我使用lerna作为包装经理管理包装和纱线。我是Azure DevOps工件的新手，我想将纱线设置为上游馈送。我已经阅读并遵循了这些步骤。有了npm，一切似乎都很好，在我的项目中输入npm后，我可以看到在azure工件中使用npm的包。但如果我用纱线，什么都不会发生。有人能帮我吗

项目.npmrc：

我也去饲料设置和添加纱线注册作为新的公共上游来源，并将其向上移动到第一上游来源。但如果我在我的项目中输入“纱线安装”，然后转到Azure工件并按源纱线过滤工件，则不会显示任何内容

npm ping与此。npmrcs：

---

我删除了%LOCALAPPDATA%\Thread\cache中的Thread缓存文件夹，以及项目根目录中的Thread.lock文件和node_模块文件夹，然后重新安装了包。我想问题是由warn.lock文件引起的。因为在warn.lock文件中为每个包指定了注册表，并且因为我没有package-lock.json npm工作，而warn没有。 在我删除Thread.lock文件之前和在image blow中重新安装软件包之后，您可以看到：

---

我删除了%LOCALAPPDATA%\Thread\cache中的Thread缓存文件夹，以及项目根目录中的Thread.lock文件和node_模块文件夹，然后重新安装了包。我想问题是由warn.lock文件引起的。因为在warn.lock文件中为每个包指定了注册表，并且因为我没有package-lock.json npm工作，而warn没有。 在我删除Thread.lock文件之前和在image blow中重新安装软件包之后，您可以看到：

registry=https://pkgs.dev.azure.com/<OrganizationName>/_packaging/<OrganizationName>/npm/registry/

always-auth=true

//pkgs.dev.azure.com/<OrganizationName>/_packaging/<OrganizationName>/npm/registry/:_authToken=blahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblahblah

path\to\project's\package.json>npm ping
npm notice PING https://pkgs.dev.azure.com/<OrganizationName>/_packaging/<OrganizationName>/npm/registry/
npm ERR! code E404
npm ERR! 404 Not Found - GET https://pkgs.dev.azure.com/<OrganizationName>/_packaging/<OrganizationName>/npm/registry/-/ping?write=true
npm ERR! 404
npm ERR! 404  'ping' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\<UserName>\AppData\Roaming\npm-cache\_logs\2020-03-27T03_20_26_797Z-debug.log

C:\WINDOWS\system32>npm ping
npm notice PING https://registry.npmjs.org/
npm notice PONG 1.296ms