Closed lidforce closed 7 months ago
It's not clear what's the actionable item here. Can you explain?
The docs are up to date. Are you saying we need to update the error message?
I think it would be worth adding, when trying to import a component, to have it immediately imported from next-client-cookies/server
instead of next-client-cookies
as it is now.
Hi, someone can help me with this error?
@LidForce I think it will be solved on the next version, when we remove support for deprecated objects. I agree it would be better to just use a different name and avoid this confusion.
For now, I would update the error message to be:
Missing `<CookiesProvider>` from "next-client-cookies/server"
@IgorCassolli I'm afraid it's not relevant for this issue. Please check our demo
folder for a working example and use StackOverflow for bugs on your setup. If you still think there is a bug on this library please open a new issue.
Released under v1.1.1
update the CookiesProvider import, the default import in VSCode is as follows:
and the import is considered deprecated. The readme says that you should specify
import { CookiesProvider } from "next-client-cookies/server";
it took me a long time to figure out why the console was constantly displaying
Because of my inattention in the readme, I didn't understand what caused the error.