Grayson Hicks

I think this is because `gatsby-plugin-sass` is hardcoding `modules: false` [here](https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-plugin-sass/src/gatsby-node.js#L38) for `.scss` files. Could be as simple as putting the `...cssLoaderOptions` after the hardcoded options there.

👋 This is also a blocker for `gatsby-plugin-preact` users trying to upgrade to Gatsby v5, which requires React 18.

I can confirm that Fly is not automatically seeding the DB when deploying with this stack. I've reached out to Fly support to see what can be changed. I believe...

For now I am getting around it this way: 1. create a `tsconfig.seed.json` for compiling the `prisma/seed.ts` to JS ```{ "include": ["./prisma/seed.ts"], "compilerOptions": { "lib": ["ES2019"], "target": "ES2019", "moduleResolution": "node",...

Hi, this should be resolved by these PRs (still pending), but will be breaking changes as part of the 1.0 release: https://github.com/mastra-ai/mastra/pull/9675 https://github.com/mastra-ai/mastra/pull/9593 https://github.com/mastra-ai/mastra/pull/9659

Made more progress on this today. Pagination now works and nodes are created, but noticed that some fields on the other API are not available on the new one (see...