nextjs - 💡(How to fix) Fix Assuming of npm registry call in dev server [1 comments, 2 participants]

TL;DR

Configure Next.js to use the internal npm proxy registry, such as Verdaccio, for consistency with the project's package manager setup.

Guidance

• Verify that the npm configuration is set to use the internal proxy registry (e.g., Verdaccio) for the project.
• Check if Next.js has an option to override the default registry URL, which might be hardcoded to npmjs.
• Investigate the hot-reloader-shared-utils.ts file to see if there's a way to pass the custom registry URL as an option or environment variable.
• Consider setting the npm_config_registry environment variable to point to the internal proxy registry before running Next.js.

Notes

The solution might require modifying the Next.js configuration or the hot-reloader-shared-utils.ts file, but without more information about the available options or APIs, it's difficult to provide a more specific fix.

Recommendation

Apply workaround: Configure the environment variable npm_config_registry to point to the internal proxy registry (e.g., Verdaccio) to ensure consistency with the project's package manager setup.