[joy-ui] Integrate Joy UI with Remix v2
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Duplicates
- I have searched the existing issues
Latest version
- I have tested the latest version
Summary 💡
I would like to see a page on the Joy UI 'Integrations' dropdown menu where there are detailed instructions on how to integrate Joy UI into an up-to-date Remix SSR application (with TypeScript, obviously).
Examples 🌈
Motivation 🔦
I switched from Vite-based React SPAs to server-side rendering. Tried both Next.js (from 13.4) and Remix (from v1.16 or something) and I believe Remix has renewed the way of developing React applications. It has an awesome DX and a growing ecosystem. I would like to continue using MUI (probably switching from Material UI to Joy UI on its production release), but I do not want crucial drawbacks because of the SSR. I have found, read and also implemented myself the material-ui-remix-ts example, but I had a really hard time integrating that one with other popular Remix-based libraries like remix-i18next because both libraries want developers to replace code parts in entry.client.tsx and entry.server.tsx. And neither do I want to spend days of figuring things out on lower levels to have them working together, because I do not feel competent enough to that task with confidence and on time yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing material-ui-remix-ts example and the issue’s notes about entry.client.tsx and entry.server.tsx. Compare the integration needs with remix-i18next, then document a current Remix SSR setup with TypeScript in a Joy UI Integrations page. Done means the page provides detailed, usable integration instructions without requiring readers to resolve conflicting entry-file changes themselves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- documentation, frontend
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100