fix: compiler error when next/cache is used in a client module (#75979)
Most functions in `next/cache` don't work on the client, and produce confusing error messages when called there. It's better to just ban them at compile time. NOTE: For legacy/compat reasons, we're allowing `unstable_cache` and `unstable_noStore`, since they don't currently throw when called.
Showing
Please
register
or
sign in
to comment