Oh just one more thing does it have to use the Next.js pages router? I thought most examples should just use the app router as it's the most recent one.
Still, the example looks great!

Also, how can I run the example in my development workflow? pnpm install seems to install in the whole project scope of the monorepo.
If we don't have instructions for doing that with a Toolpad Core example I guess we could add them later separately?
Also not sure if that means that Core and Studio examples should be separated in different folders.

Oh just one more thing does it have to use the Next.js pages router? I thought most examples should just use the app router as it's the most recent one. Still, the example looks great!

I used the pages router assuming most people using next-auth@4 would be interested in maintaining older apps they created with the pages router, but I can add a version with the app router as well. Perhaps we can introduce the choice to choose between next-auth versions in the CLI, as well. Wdyt @Janpot?

Also, how can I run the example in my development workflow? pnpm install seems to install in the whole project scope of the monorepo. If we don't have instructions for doing that with a Toolpad Core example I guess we could add them later separately? Also not sure if that means that Core and Studio examples should be separated in different folders.

For testing during development, the method would be akin to testing the playground apps, i.e.,

• modifying the @toolpad/core dependency in the example to workspace/*
• adding the example to the workspace in pnpm-workspace.yml, like examples/<example-name>
• run the project in a separate process through pnpm --filter @toolpad/core dev
• running pnpm dedupe && pnpm --filter examples/<example-name> dev to run the example

Don't know if this merits space in the contributing instructions?

Oh just one more thing does it have to use the Next.js pages router? I thought most examples should just use the app router as it's the most recent one. Still, the example looks great!

I used the pages router assuming most people using next-auth@4 would be interested in maintaining older apps they created with the pages router, but I can add a version with the app router as well. Perhaps we can introduce the choice to choose between next-auth versions in the CLI, as well. Wdyt @Janpot?

That's a good point, feel free to stick with that option then, I guess we can't really know for sure what's best for now.

Also, how can I run the example in my development workflow? pnpm install seems to install in the whole project scope of the monorepo. If we don't have instructions for doing that with a Toolpad Core example I guess we could add them later separately? Also not sure if that means that Core and Studio examples should be separated in different folders.

For testing during development, the method would be akin to testing the playground apps, i.e.,

• modifying the @toolpad/core dependency in the example to workspace/*
• adding the example to the workspace in pnpm-workspace.yml, like examples/<example-name>
• run the project in a separate process through pnpm --filter @toolpad/core dev
• running pnpm dedupe && pnpm --filter examples/<example-name> dev to run the example

Don't know if this merits space in the contributing instructions?

Probably not super urgent but the current instructions there are about Toolpad Studio only.
We should probably cover all of this in a single more generic section now.

Updated to add instructions to run the playground apps (and examples) for Toolpad Core.

I've explored integrating next-auth v4 with the app router, and the chief problem is that they do not provide a server-side signIn equivalent function; the recommended approach is to use your own, wherein there continue to be multiple issues: nextauthjs/next-auth#45

I've explored integrating next-auth v4 with the app router, and the chief problem is that they do not provide a server-side signIn equivalent function; the recommended approach is to use your own, wherein there continue to be multiple issues: nextauthjs/next-auth#45

Sticking with the pages router should be cool!