Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

README not being shown for packages (pnpm 6 only)

See original GitHub issue

Your Environment

verdaccio version: 5.1.6
node version [12.x.x, 14.x.x]: 14.15.5
package manager: pnpm@6
os: Linux

Describe the bug

Verdaccio is not showing the README for packages that I publish to the registry. I can download the tarball directly and verify that the README does exist, but the Verdaccio UI always displays this now:

ERROR: No README data found!

To Reproduce

Publish a package and then open the UI.

Expected behavior

The UI should be showing the README.

Configuration File (cat ~/.config/verdaccio/config.yaml)

# https://github.com/verdaccio/verdaccio/issues/301
server:
  keepAliveTimeout: 0
# path to a directory with all packages
storage: (redacted)
web:
  title: (redacted)
security:
  api:
    legacy: false
    jwt:
      sign:
        expiresIn: 30d
  web:
    legacy: false
    sign:
      expiresIn: 7d
auth:
  htpasswd:
    file: (redacted)
    max_users: -1
  ldap:
    type: ldap
    cache:
      # max credentials to cache (default to 100 if cache is enabled)
      size: 100
      # cache expiration in seconds (default to 300 if cache is enabled)
      expire: 300
    client_options:
      url: (redacted)
      searchBase: (redacted)
      searchFilter: (redacted)
      reconnect: true
# a list of other known repositories we can talk to
uplinks:
  npmjs:
    url: https://registry.npmjs.org/
    max_fails: 100
    maxage: 2h
  fontAwesome:
    url: https://npm.fontawesome.com/
    max_fails: 100
    maxage: 2h
    auth:
      type: bearer
      token_env: FONT_AWESOME_NPM_TOKEN
packages:
  '@arista/*':
    access: $all
    publish: $authenticated
    proxy: npmjs
  '@fortawesome/*':
    access: $all
    proxy: fontAwesome
  '@*/*':
    # scoped packages
    access: $all
    publish: $authenticated
    proxy: npmjs
  '**':
    # allow all users (including non-authenticated users) to read and
    # publish all packages
    #
    # you can specify usernames/groupnames (depending on your auth plugin)
    # and three keywords: "$all", "$anonymous", "$authenticated"
    access: $all
    # allow all known users to publish packages
    # (anyone can register by default, remember?)
    publish: $authenticated
    # if package is not available locally, proxy requests to 'npmjs' registry
    proxy: npmjs
# Use `npm audit`
middlewares:
  audit:
    enabled: true
logs: {type: stdout, format: pretty, level: http}
listen: (redacted)

Environment information

Environment Info:
  System:
    OS: Linux 4.19 Alpine Linux
    CPU: (40) x64 Intel(R) Xeon(R) CPU E5-2670 v2 @ 2.50GHz
  Binaries:
    npm: 6.14.14 - /usr/local/bin/npm
{"level":30,"time":1634060285178,"pid":107,"hostname":"npm-0","msg":"exit caught"}

Debugging output

Can furnish upon request.

Contribute to Verdaccio

I’m willing to fix this bug 🥇

Issue Analytics

State:
Created 2 years ago
Comments:12 (6 by maintainers)

Top GitHub Comments

1reaction

kaiyomacommented, Dec 16, 2021

~@juanpicado I just tried publishing packages with version 6.24.1 of pnpm and the same problem persists. Verdaccio is reporting ERROR: No README data found!~

Edit: never mind, I had forgotten to update all copies of pnpm. Once I upgraded everything to 6.24.1, the README files started appearing again in Verdaccio. Thanks for the fix!

1reaction

kaiyomacommented, Oct 20, 2021

Sounds good. Let me know if I can be helpful.

Top Results From Across the Web

Filtering | pnpm

Filtering allows you to restrict commands to specific subsets of packages. pnpm supports a rich selector syntax for picking packages by name or...

README.md - Aspect's Bazel Documentation

Fast: Bazel's sandbox only sees npm packages as directories, not individual files. ... https://blog.aspect.dev/rulesjs-npm-benchmarks shows benchmarks for ...

Axios - npm

TypeScript icon, indicating that this package has built-in type declarations ... `data` is the data to be sent as the request body //...

node.js - E: Unable to locate package npm - Stack Overflow

It only installs a nodejs binary. So, if you only type sudo apt-get install nodejs , it does not install other goodies such...

A story of how we migrated to pnpm - ‹div›RIOTS

There's just one gotcha when you're using it in a monorepo: the workspaces have to be declared in your pnpm-workspace.yaml first. If you...