[pigment-css][example] Add example project with Remix

[brijeshb42]

#39765

[mui-bot]

Netlify deploy preview

https://deploy-preview-41700--material-ui.netlify.app/

Bundle size report

No bundle size changes (Toolpad)
No bundle size changes

Generated by 🚫 dangerJS against 81066fd

[mnajdova]

Let's revert the change to apps/pnpm-lock.yml, it's not related

[mnajdova]

This reminds that we need to update all examples to use the next tag. I will handle this in a separate PR.

[siriwatknp]

I think Remix should be added to apps/pigment-css-remix-app too, it can be the same PR or a separate one, your call!

[mnajdova]

I think Remix should be added to apps/pigment-css-remix-app too, it can be the same PR or a separate one, your call!

Agree! I will leave few questions here, even tough they are not 100% related to the PR:

• should we add a CI step that build the apps/ projects and fails if it's not successful? We are very often breaking these examples while working on Pigment CSS, it could be a two steps validation that the changes work
• how do we make sure that when we fix something in the apps/ directory we also update the examples if needed? I am not regularly checking if they are working, but taking into account how often we break the apps/ I won't be surprised if they are breaking from time to time with some changes

[brijeshb42]

should we add a CI step that build the apps/ projects

This is already the case and part of the current CI build. Both vite and next.js apps are built. The previous propTypes issue was failing in dev environment. And in most cases, the actual fix lies in the package code and rarely in the app code. So it should get autofixed since we always tag the latest release.

how do we make sure that when we fix something in the apps...

The example app is very minimal and doesn't cover complex use-case which is part of our current apps/ dir. But I agree that in future, when we expand the example apps to cover more use-cases, we'll also need to update the examples.

[brijeshb42]

IMO, we can just convert the Vite app to a remix one. It'll provide coverage for both and we won't need to use the custom vite plugin for routing as Remix will already handle that.

[siriwatknp]

IMO, we can just convert the Vite app to a remix one. It'll provide coverage for both and we won't need to use the custom vite plugin for routing as Remix will already handle that.

Nice!

[siriwatknp]

👍