React 19: Fails to install

[larson-carter]

Overview

When installing remix-run/[email protected] into a React 19.0.0 project it fails. I have tried a variety of solutions(Listed below), I hope this is not a duplicate question/issue - any help is welcomed. I am just sorta new to this type of development, thank you all!

The Reasoning

• Migrating already existing Remix project and React to latest versions.
• Going through dependency and issue hell.
• This is my last and final package to complete my upgrades (I think!)

Logging

• Here are the logs from running npm install:

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: undefined@undefined
npm error Found: [email protected]
npm error node_modules/react
npm error   react@"^19.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0.0" from @remix-run/[email protected]
npm error node_modules/@remix-run/react
npm error   @remix-run/react@"2.15.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /Users/larsoncarter/.npm/_logs/2025-01-02T19_28_26_173Z-eresolve-report.txt
npm error A complete log of this run can be found in: /Users/larsoncarter/.npm/_logs/2025-01-02T19_28_26_173Z-debug-0.log

What have I tried

I have tried a lot of things but not limited to:

• ChatGPT.
• Searching for other discussions/issues.
• Seeing other discussion forums.
• Confusing myself with React/Remix and Router (I am new and overwhelmed sorta)
• Tried using --force and --legacy-peer-deps

[trinh-junecare]

just followed the installation instruction from the doc here and got the same failure

[larson-carter]

Thank you for validating my concern.

I just left another comment to hopefully start a thread to cover what I am speculating of what will happen. Is this the end of Remix?

[larson-carter]

This might be a further technical consideration from Remix as a whole...

Is remix going away since react router 7 is taking over what remix used to be?

Would like to see an official response on if us remix adopters need to consider remix upgrades or if we should ditch it and migrate to purely react with its new router?

[Nahiek]

I tried to upgrade react, vite, and typescript. But I could not do because remix does not use the latest version of them as pear dependencies.

remix-run/react: 15.0.2 uses react:18.0.0 as pear dependency.

  "peerDependencies": {
    "react": "^18.0.0",
    "react-dom": "^18.0.0",
    "typescript": "^5.1.0"
  },

It can be overridden.

  "overrides": {
    "@remix-run/react": {
      "react": "$react",
      "react-dom": "$react-dom"
    }
  }

@remix-run/dev uses "typescript": "^5.1.0", "vite": "^5.1.0" as pear dependencies.

  "peerDependencies": {
    "@remix-run/react": "^2.15.2",
    "@remix-run/serve": "^2.15.2",
    "typescript": "^5.1.0",
    "vite": "^5.1.0",
    "wrangler": "^3.28.2"
  },

We have to wait til they update the packages.

[Kouji-Koike]

For example, wouldn't importing from react-router-dom make @remix-run/react unnecessary?

[Trikooo]

@larson-carter - it's April 2025 and I ran into the same issue when trying to use Remix with React 19.

The simplest solution for me was just downgrading to React 18:

npm uninstall react react-dom
npm i react@^18.2.0 react-dom@^18.2.0

After downgrading, I was able to install Remix without any issues. I know you mentioned trying various solutions, but sometimes the simplest approach works best until Remix officially supports React 19.
I wouldn't worry too much about Remix vs React Router 7. They're from the same team, and Remix builds on top of React Router to provide additional features. No need to rush into ditching Remix!

[Nahiek]

There won't be a new version of Remix. Use react-router 7.
https://reactrouter.com/upgrading/remix