0

I find that dependencies are prefixed with registry path like blew:

packages:

  registry.npmmirror.com/@ampproject/remapping/2.2.0:
    resolution: {integrity: sha512-qRmjj8nj9qmLTQXXmaR1cck3UXSRMPrbsLJAasZpF+t3riI71BXed5ebIOYwQntykeZuhjsdweEc9BxH5Jc26w==, registry: https://registry.npm.taobao.org/, tarball: https://registry.npmmirror.com/@ampproject/remapping/-/remapping-2.2.0.tgz}
    name: '@ampproject/remapping'
    version: 2.2.0
    engines: {node: '>=6.0.0'}
    dependencies:
      '@jridgewell/gen-mapping': registry.npmmirror.com/@jridgewell/gen-mapping/0.1.1
      '@jridgewell/trace-mapping': registry.npmmirror.com/@jridgewell/trace-mapping/0.3.15
    dev: true

does it means that the project will install packages with the registry?

but i find there is no registry path in another project's lock file

packages:

  /@ampproject/remapping/2.2.0:
    resolution: {integrity: sha512-qRmjj8nj9qmLTQXXmaR1cck3UXSRMPrbsLJAasZpF+t3riI71BXed5ebIOYwQntykeZuhjsdweEc9BxH5Jc26w==}
    engines: {node: '>=6.0.0'}
    dependencies:
      '@jridgewell/gen-mapping': 0.1.1
      '@jridgewell/trace-mapping': 0.3.17
    dev: true

how did that come about? please help

ShengjieLu
  • 89
  • 1
  • 2
  • I found that I even have some packages prefixed with `registry.npmjs.org/`. In my case, it looks like it happens when we have some packages from the external package repository, but it uses packages directly from the npm registry. Do you have any packages in your repo that uses deps from external package repositories? – Pavlo Zhukov May 04 '23 at 08:37

0 Answers0