Help Migrating from @remix-run/architect to @react-router/architect

[alexkads]

Hello everyone,

I'm currently using Remix with @remix-run/architect, and I'd like to migrate my setup to React Router using the new @react-router/architect package.

Additionally, I am using GitHub Actions for my CI/CD pipeline and would like to ensure that the migration won't cause any disruptions or compatibility issues in my workflows.

I couldn't find clear documentation or guidelines about this specific migration path, so I'd greatly appreciate any insights or tips on the following:

Are there breaking changes I should be aware of during this migration?

What would be the best approach to smoothly transition from Remix's Architect to React Router's Architect?

Are there any known pitfalls or compatibility issues, especially regarding CI/CD with GitHub Actions?

Any guidance or references to relevant resources would be extremely helpful!

Thanks in advance!

[mclngl]

@alexkads hey we're in the same situation, did you ever find out ?

[alexkads]

@mclngl Hi! Unfortunately, I gave up on AWS Architect and ended up migrating my page to Vercel with ReactRouter7 SSR.