Brandon Bayer
Brandon Bayer
Related blitz-js/legacy-framework#466
@clearink I think the original issue might be fixed. But regardless, I'm sure there's a way to fix it. No-one has had time to dig into it yet, but anyone...
Solution is to add https://github.com/williamluke4/next-prisma-plugin to our [`withBlitz`](https://github.com/blitz-js/blitz/blob/canary/packages/server/src/with-blitz.ts) webpack wrapper and to remove the `globalThis` stuff from [the new app template](https://github.com/blitz-js/blitz/blob/canary/packages/generator/templates/app/db/index.ts).
Hey @tconroy, I haven't added `next-prisma-plugin` yet because it's still experimental from prisma and I don't know if it works with webpack 5. Also it doesn't it with our `globalThis`...
should be resolved with blitz 2.0
I vote for `Routes.Post().href`. `href` matches other nextjs/blitz href usage and also `new Url()` usage.
@margalit should that be a separate field? I'm not personally sure of which places nextjs automatically handles basePath and which they don't.
Hey @Slein2012. The console warning is expected (see https://github.com/blitz-js/legacy-framework/issues/56). But if we are having styling issues, then that is a problem. Can you provide exact steps to reproduce the styling...
Also please test with Blitz `0.40.0` and report back
Closing, same response as: https://github.com/blitz-js/blitz/issues/3767#issuecomment-1230341547