nextjs - 💡(How to fix) Fix Importing/running cached functions in proxy.ts [2 comments, 3 participants]

Currently, I get the following error in the terminal and as a popup when running next dev: cacheLife is in fact being called inside a "use cache" function and it works as expected if I use the function in any other place than proxy.ts. The error message implies that the issue is that the function doesn't have "use cache", but it seems to have more to do with the usage inside of proxy.ts.

TL;DR

The issue is likely due to the cacheLife function being called outside of a valid React context in proxy.ts, and a workaround may involve reorganizing the code to ensure cacheLife is called within a React component or a custom hook.

Guidance

• Verify that cacheLife is indeed being called within a "use cache" function in proxy.ts by checking the code and any potential higher-order functions or wrappers.
• Consider reorganizing the code to ensure cacheLife is called within a React component or a custom hook, as the error message suggests it requires a specific context.
• Investigate if there are any specific restrictions or limitations on using cacheLife within proxy.ts or Next.js middleware.
• Check the Next.js documentation and any related issues on GitHub to see if this is a known limitation or bug.

Example

No code example is provided as the issue is more related to the context and usage of cacheLife rather than a specific code snippet.

Notes

The issue seems to be specific to the next dev stage and proxy.ts file, and may not be a general problem with the cacheLife function. Further investigation is needed to determine the root cause and a suitable solution.

Recommendation

Apply workaround: Reorganize the code to ensure cacheLife is called within a valid React context, as this is the most likely solution based on the error message and the context of the issue.