Summary
Remix v1.17 (released 2023) is end-of-life. The ecosystem has moved to Remix v2 / React Router v7. This repo needs a coordinated migration.
Dependabot PRs #18 and #19 attempted to bump individual @remix-run/* packages from v1 to v2 but were closed — this migration cannot be done piecemeal.
Packages to Upgrade
All @remix-run/* packages must be upgraded together:
| Package |
Current |
Target |
@remix-run/react |
1.17.1 |
2.x |
@remix-run/node |
1.17.1 |
2.x |
@remix-run/dev |
1.17.1 |
2.x |
@remix-run/serve |
1.17.1 |
2.x |
@remix-run/css-bundle |
1.17.1 |
2.x |
@remix-run/eslint-config |
1.17.1 |
2.x |
Migration Steps
Based on the Remix v2 upgrade guide:
- Audit
@myst-theme compatibility — @myst-theme/* v0.14.0 may depend on Remix v1 APIs. Check if upstream supports v2 before proceeding.
- Enable v2 future flags — Already partially done (
v2_routeConvention, v2_errorBoundary, v2_normalizeFormMethod, etc. are enabled in remix.config.dev.js). Verify all flags are set.
- Migrate config —
remix.config.js (CJS) → vite.config.ts. Remove the separate dev/prod config pattern.
- Update route conventions — Verify existing routes in
app/routes/ follow v2 flat-file conventions (they likely already do given the future flags).
- Update imports — Some APIs moved between packages in v2.
- Update
entry.server.tsx and entry.client.tsx — v2 has updated entry file patterns.
- Test thoroughly — No CI exists yet (tracked separately), so manual testing is essential.
Positive Signs
The current codebase already enables several v2 future flags in remix.config.dev.js:
v2_routeConventionv2_errorBoundaryv2_normalizeFormMethodv2_meta
This means much of the migration groundwork is already in place.
Blocker
@myst-theme compatibility must be verified first. If @myst-theme/* v0.14.0 doesn't support Remix v2, this migration is blocked until upstream updates.
Related
Summary
Remix v1.17 (released 2023) is end-of-life. The ecosystem has moved to Remix v2 / React Router v7. This repo needs a coordinated migration.
Dependabot PRs #18 and #19 attempted to bump individual
@remix-run/*packages from v1 to v2 but were closed — this migration cannot be done piecemeal.Packages to Upgrade
All
@remix-run/*packages must be upgraded together:@remix-run/react@remix-run/node@remix-run/dev@remix-run/serve@remix-run/css-bundle@remix-run/eslint-configMigration Steps
Based on the Remix v2 upgrade guide:
@myst-themecompatibility —@myst-theme/*v0.14.0 may depend on Remix v1 APIs. Check if upstream supports v2 before proceeding.v2_routeConvention,v2_errorBoundary,v2_normalizeFormMethod, etc. are enabled inremix.config.dev.js). Verify all flags are set.remix.config.js(CJS) →vite.config.ts. Remove the separate dev/prod config pattern.app/routes/follow v2 flat-file conventions (they likely already do given the future flags).entry.server.tsxandentry.client.tsx— v2 has updated entry file patterns.Positive Signs
The current codebase already enables several v2 future flags in
remix.config.dev.js:v2_routeConventionv2_errorBoundaryv2_normalizeFormMethodv2_metaThis means much of the migration groundwork is already in place.
Blocker
@myst-themecompatibility must be verified first. If@myst-theme/*v0.14.0 doesn't support Remix v2, this migration is blocked until upstream updates.Related