nextjs - 💡(How to fix) Fix Docs: Nexjs Version page in npm is innaccessible due to the amount of versions [2 comments, 3 participants]

TL;DR

The issue can be mitigated by using the npm registry API or a third-party tool to retrieve the version history of the Next package.

Guidance

• Consider using the npm registry API to fetch the version history of the Next package, which may be more efficient than loading the entire versions page.
• Reach out to the npmjs.com team to report the issue with the versions page hanging and not fully loading.
• Look into using a package manager like npm or yarn with a built-in command to list available versions of a package, which may provide an alternative way to view version history.
• Check if there are any existing issues or discussions on the npmjs.com or Next.js repositories related to this problem.

Notes

The issue seems to be related to the npmjs.com website performance rather than a specific problem with the Next.js package or Vercel.

Recommendation

Apply workaround: Use the npm registry API or a third-party tool to retrieve the version history, as this provides an alternative solution to viewing the version history without relying on the npmjs.com website.