Support either Remix ^1.0.0 or ^2.0.0

[lpsinger]

Remix 2.0.0 is coming out very soon --- prereleases are coming out. Allow the peer dependencies to be met by Remix v1 or v2.

[tommyasai]

@balavishnuvj I recently attempted to install @balavishnuvj/remix-seo alongside the newly released Remix version 2.0.0-pre.x, but encountered a peer dependency conflict.

I'd like this PR to be merged and released to fix the issue. If there's a workaround I could use in the meantime, I'd appreciate some guidance.

[lpsinger]

I think that the reason for the peer dependency conflict is that the prereleases cannot satisfy the dependency.

[tommyasai]

@lpsinger Noted. I use --legacy-peer-deps as a temporary solution

[tommyasai]

FYI: Upgraded to remix v2.0.0 but I am seeing the same error.

#11 4.700 npm ERR! While resolving: @balavishnuvj/[email protected]
#11 4.700 npm ERR! Found: @remix-run/[email protected]
#11 4.700 npm ERR! node_modules/@remix-run/react
#11 4.700 npm ERR!   @remix-run/react@"^2.0.0" from the root project
#11 4.700 npm ERR! 
#11 4.700 npm ERR! Could not resolve dependency:
#11 4.700 npm ERR! peer @remix-run/react@"^1.0.0" from @balavishnuvj/[email protected]
#11 4.700 npm ERR! node_modules/@balavishnuvj/remix-seo
#11 4.700 npm ERR!   @balavishnuvj/remix-seo@"^1.0.2" from the root project
#11 4.700 npm ERR! 
#11 4.700 npm ERR! Conflicting peer dependency: @remix-run/[email protected]
#11 4.700 npm ERR! node_modules/@remix-run/react
#11 4.700 npm ERR!   peer @remix-run/react@"^1.0.0" from @balavishnuvj/[email protected]

[lpsinger]

:shrug: It's working for me now that Remix 2.0.0 is out. See https://github.com/nasa-gcn/gcn.nasa.gov/pull/1377.

[tommyasai]

Thanks. I switched to your fork and it worked. 🙏

[lpsinger]

This is fixed in our fork: https://github.com/nasa-gcn/remix-seo