What is the easiest path for migrating an existing CRA app to Remix?

[YPCrumble]

First, thank you for building and maintaining RR and Remix! I've been a longtime CRA/React Router user and this is the successor project I'm most excited about, besides Vite, and now it even looks like you've integrated Vite!

I have an existing CRA app and was excited to hear that Remix will be merging with React Router. I'm running a fairly customized CRA application that uses React Router v6 as well as some custom code to server render the app.

I'd love to upgrade to use Remix, but I'd like to avoid what looks like a pretty large migration to adapt my routes (https://remix.run/docs/en/main/guides/migrating-react-router-app).

Will waiting for the release of React Router v7 remove the need to do any major migration, as I understand that v6 to v7 should be fairly easy? Is there a timeline for when v7 is expected to be released? Or should I go ahead now and follow the migration to Remix before v7 is released?

Thanks for any advice or guidance!

[YPCrumble]

Figured out the answer to my question via Discord. Basically I need to wait for RRv7

in RRv7 there will be a routes.ts file where you can define your routes similar to createBrowserRouter, but there will also be functions to keep the current file based convention, the idea from what I saw is that you will be able to use any convention you want with some defaults provided to you

If you want to avoid Remix's current file convention then wait for RRv7, otherwise you can change your code so you have a routes folder following current convention and in a routes.ts call createBrowserRouter, once you migrate to Remix you can remove the file using createBrowserRouter