Just want to report an issue that took me a good bit of time to debug:
• When using codegen you cannot use the next.js loader, as it requires options that break the user data context from being properly set
• The supabase auth codegen example does this, but it doesn’t have comments or docs, and I also don’t see docs on the docs site
• I understand now what is going on and that the fact that it requires a loader is a sign that it is dynamically loading components and not in codegen, but it is a bit of a sharp edge
adding to this; I think another difficulty is that the create-plasmic-app only has the feature for creating an app using app routing in loader mode, so if you’re trying to start using plasmic and understand what the folder and file structure would be for nextjs routing with app; you’re likely going to start it with loader to begin with
We don’t actually recommend using plasmic with the app router and codegen at the moment, as we can’t support extracting query data at build time with the app router. So you’ll have to use the /pages router with plasmic for now