kevinmitch14
kevinmitch14
Have you tried `experimental: { esmExternals: false }` in your next.config?
Adding the following stopped the warning messages. Using `"@libsql/client": "^0.3.5"` ```js const nextConfig = { experimental: { serverComponentsExternalPackages: ["@libsql/client"] } } ``` It looks like this will be automatically handled...
This would be extremely helpful! Currently having similar issues
Is it safe to say there is no trivial way to accomplish this?
And in the case of using the nextjs library version, with a custom UI, is it possible to use to use `authMiddleware`? Because we do not want to use hosted...
Hey Paul, the reason is `invalid_jwt`. I think it is because, the updated cookie in middleware is not directly available in the route handler. I believe this is why there...
Could you confirm if this example actually works? I am getting really strange results here. Debug logs say session is valid, but when I check `getSession()` like in the docs,...
Could be related to https://github.com/clerk/javascript/pull/3001
Hey @dimkl what I've found is that as soon as you pass a custom `publishableKey` in middleware. Eg. `publishableKey: process.env.CUSTOM_PK_NAME` or even hardcoding the publishableKey (`publishableKey: "..."`). You get the...
> Hello @dcyoung , We have attempted to solve the current issue in our new major version `@clerk/[email protected] ` (currently in beta). Check the following example: > This still does...