Can't find package

[SageKwun]

I published a package in my own verdaccio. It can be searched by npm:

but I can't install it:

It's sure it is in my storage

I run verdaccio by official docker image: verdaccio/verdaccio:5.31 and it's my config:

docker-compose.yml

  verdaccio:
    image: verdaccio/verdaccio:5.31
    container_name: "verdaccio"
    user: root
    environment:
      # VERDACCIO 服务端口
      - VERDACCIO_PORT=3005
      # 当前登录 linux 服务器的用户名
      - VERDACCIO_USER_NAME="root" 
    ports:
      # 宿主和容器的端口
      - "3005:3005"
    volumes:
      - "./storage:/verdaccio/storage"
      - "./config:/verdaccio/conf"
      - "./plugins:/verdaccio/plugins"

config.yaml

storage: /verdaccio/storage
auth:
  htpasswd:
    file: /verdaccio/conf/htpasswd
uplinks:
  server2:
    url: https://registry.npmmirror.com
  npmjs:
    url: https://registry.npmjs.org/
packages:
  '@*/*':
    access: $all
    publish: $authenticated
    proxy: server2
  '**':
    # 这里如果不设置在使用 npm i xxx、 npm publish 时将会提示包不存在，为了方便这里直接设置上如下两行
    access: $all
    publish: $authenticated
    proxy: server2
logs:
  - {type: stdout, format: pretty, level: http}
listen:
  # 这个端口务必对应上
  - 0.0.0.0:3005

[juanpicado]

Sometimes the client side cache might be the issue,

• ensure you have clean up local cache
• enable debug logging in the package manager to see more in detail what's going on
• you can reach the metadata with http://registry/@nestjs-lark/lark and inspect the metadata if the version you want is there
• increase logging on verdaccio

Try that let me know

[SageKwun]

Sometimes the client side cache might be the issue,

• ensure you have clean up local cache
• enable debug logging in the package manager to see more in detail what's going on
• you can reach the metadata with http://registry/@nestjs-lark/lark and inspect the metadata if the version you want is there
• increase logging on verdaccio

Try that let me know

I run pnpm store prune --force to clean up local cache

but it seemed not work, and there is no logs in docker logs

however, I can get meta info

and I can successfully install this package in another machine

[juanpicado]

have you tested with other package managers? to be sure is not a isolated issue

[SageKwun]

It might be that there is no .npmrc file in my sub package which is in a monorepo. And I delete the package-lock.yaml, finally, it works, thank you for your help!

[juanpicado]

Using the flag --registry with any npm/pnpm command is always a safeguard, unfortunately does not work with modern yarn anymore but always use that to confirm the issue is not in another place.