Post

Not many npm packages run into this problem, but there is a maximum metadata size for all versions of a package. If you exceed it, you can't publish that pkg anymore 😰 Since we publish next@canary daily, we don't wan to hit this ceiling. github.com/vercel/next....

github.com[cd] reduce size of npm metadata on publish by styfle · Pull Request #94953 · vercel/next.jsThe maximum size of the npm package metadata for all versions of that package is 100 MB. We are currently over 30MB as seen here: curl -w '%{size_download}' -so /dev/null https://registry.n...

You can check the size of this metadata using the following script curl -w '%{size_download}' -so /dev/null registry.npmjs.org/next | awk '{print $1/1000000 " MB"}'

0 reposts2 likes

No replies yet.