unhandledRejection: Error: Cannot find module 'lru-cache' about next.js

[icyJoseph]

Do you mean that you used it without having it installed, aka in your package.json? If so, then just install it yourself, I see in the examples, an app that uses lru-cache, https://github.com/vercel/next.js/blob/fedb675520e0de8f360f8d2e262acdf76b4f0491/examples/api-routes-rate-limit/package.json, you should use it as such.

I reckon that you got impacted by vendor-ing of the package. Next.js still has it, but as a compiled dependency, so that we, the users, don't need to download and reinstall it every time. However, that belongs to the internals of the framework, and you should not rely on that. Install the package on your project, and take it from there.

[champ6803]

Do you mean that you used it without having it installed, aka in your package.json? If so, then just install it yourself, I see in the examples, an app that uses lru-cache, https://github.com/vercel/next.js/blob/fedb675520e0de8f360f8d2e262acdf76b4f0491/examples/api-routes-rate-limit/package.json, you should use it as such.

I reckon that you got impacted by vendor-ing of the package. Next.js still has it, but as a compiled dependency, so that we, the users, don't need to download and reinstall it every time. However, that belongs to the internals of the framework, and you should not rely on that. Install the package on your project, and take it from there.

Nextjs has an announcement space? Is there anything about update dependencies? If so, where should I follow them?

[icyJoseph]

I think, from a project point of view, you are over stepping your boundaries, if you want to rely on a transient dependency like that. Such packages are never part of the project's public API, and because of that, it is your sole responsibility to deal with the consequences of having done so.

[ztanner]

Hi -- if your project depends on lru-cache, you should install it in your project. Next.js uses it internally, but as @icyJoseph mentioned, you should not rely on Next.js providing it. We have not removed this dependency from our internal usage, and without a link to a reproduction, we're not able to help debug further.

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.