Sina Neda
Sina Neda
@Rizzato95 Thanks! How did you configure the URLs on Supabase? Site URL, and then both localhost and base url in the Redirect URLs?
> @brunopbarbosa I'm running into the same issue with Nuxt 3, did u find a solution? You can try to bypass this issue for the affected component by wrapping it...
This is indeed an ongoing issue. 500 error being returned in local, but works fine in prod.
**Update**: Found solution to the issue. Add the following ```overrides``` in your ```package.json``` and run ```pnpm install``` ```json "pnpm": { "overrides": { "sharp": "0.33.4" } } ```
The `documentDriven` mode is a big issue in its current experimental state when using both `/pages` and `/content` in tandem. The workaround is to set `documentDriven: false` for all slug...
The latest `@supabase/supabase-js` has a dual CommonJS/ESM distribution and Vite seems to be failing the pre-bundling of Supabase pakages during dev (hence causing the browser to load the CommonJS version...
Wild. I can confirm that this appears to be a comprehensive log of most user actions/prompts in the CLI. I cannot find any documentation about it on their site.
I wonder if the data displayed when running `/status` is cached in the aforementioned log file!?