Internal server error: Failed to load url crypto

Open
#210 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, react, typescript, vite
Domain
devtools, tooling

Research direction

Reproduce the reload failure after adding the package to vite.config.ts, using the reported Node.js and Yarn versions. Start by inspecting how node_modules/.vite/deps_ssr/react-router-devtools_client.js resolves crypto during SSR. Done means the development server reloads without the Vite internal server error.

Written by the indexing model from the issue text.

Description

After installing this and adding it to my vite.config.ts, a reload results in:

...
[vite] Internal server error: Failed to load url crypto (resolved id: crypto) in  node_modules/.vite/deps_ssr/react-router-devtools_client.js. Does the file exist?
...
> node -v
v22.16.0
> yarn -v
4.9.1

> yarn info react-router               
└─ react-router@npm:7.6.2
   ├─ Instances: 1
   ├─ Version: 7.6.2
   │ 
   └─ Dependencies
      ├─ cookie@npm:^1.0.1 → npm:1.0.2
      └─ set-cookie-parser@npm:^2.6.0 → npm:2.7.1
> yarn info @react-router/dev
└─ @react-router/dev@npm:7.5.3
   ├─ Instances: 1
   ├─ Version: 7.5.3
   │ 
   ├─ Exported Binaries
   │  └─ react-router
   │ 
   └─ Dependencies
      ├─ @babel/core@npm:^7.21.8 → npm:7.27.4
      ├─ @babel/generator@npm:^7.21.5 → npm:7.27.5
      ├─ @babel/parser@npm:^7.21.8 → npm:7.27.5
      ├─ @babel/plugin-syntax-decorators@npm:^7.22.10 → npm:7.27.1
      ├─ @babel/plugin-syntax-jsx@npm:^7.21.4 → npm:7.27.1
      ├─ @babel/preset-typescript@npm:^7.21.5 → npm:7.27.1
      ├─ @babel/traverse@npm:^7.23.2 → npm:7.27.4
      ├─ @babel/types@npm:^7.22.5 → npm:7.27.6
      ├─ @npmcli/package-json@npm:^4.0.1 → npm:4.0.1
      ├─ @react-router/node@npm:7.5.3 → npm:7.5.3
      ├─ arg@npm:^5.0.1 → npm:5.0.2
      ├─ babel-dead-code-elimination@npm:^1.0.6 → npm:1.0.10
      ├─ chokidar@npm:^4.0.0 → npm:4.0.3
      ├─ dedent@npm:^1.5.3 → npm:1.6.0
      ├─ es-module-lexer@npm:^1.3.1 → npm:1.7.0
      ├─ exit-hook@npm:2.2.1 → npm:2.2.1
      ├─ fs-extra@npm:^10.0.0 → npm:10.1.0
      ├─ jsesc@npm:3.0.2 → npm:3.0.2
      ├─ lodash@npm:^4.17.21 → npm:4.17.21
      ├─ pathe@npm:^1.1.2 → npm:1.1.2
      ├─ picocolors@npm:^1.1.1 → npm:1.1.1
      ├─ prettier@npm:^2.7.1 → npm:2.8.8
      ├─ react-refresh@npm:^0.14.0 → npm:0.14.2
      ├─ semver@npm:^7.3.7 → npm:7.7.2
      ├─ set-cookie-parser@npm:^2.6.0 → npm:2.7.1
      ├─ valibot@npm:^0.41.0 → npm:0.41.0
      └─ vite-node@npm:3.0.0-beta.2 → npm:3.0.0-beta.2
x yarn info react-router-devtools
└─ react-router-devtools@npm:5.0.6
   ├─ Instances: 1
   ├─ Version: 5.0.6
   │ 
   └─ Dependencies
      ├─ @babel/core@npm:^7.26.10 → npm:7.27.4
      ├─ @babel/generator@npm:^7.26.5 → npm:7.27.5
      ├─ @babel/parser@npm:^7.26.10 → npm:7.27.5
      ├─ @babel/traverse@npm:^7.26.10 → npm:7.27.4
      ├─ @babel/types@npm:^7.26.10 → npm:7.27.6
      ├─ @biomejs/cli-darwin-arm64@npm:^1.9.4 → npm:1.9.4
      ├─ @radix-ui/react-accordion@npm:^1.2.2 → npm:1.2.11
      ├─ @radix-ui/react-select@npm:^2.1.5 → npm:2.2.5
      ├─ @rollup/rollup-darwin-arm64@npm:^4.32.1 → npm:4.42.0
      ├─ @rollup/rollup-linux-x64-gnu@npm:^4.32.1 → npm:4.42.0
      ├─ beautify@npm:^0.0.8 → npm:0.0.8
      ├─ bippy@npm:^0.3.7 → npm:0.3.16
      ├─ chalk@npm:^5.4.1 → npm:5.4.1
      ├─ clsx@npm:^2.1.1 → npm:2.1.1
      ├─ date-fns@npm:^4.1.0 → npm:4.1.0
      ├─ framer-motion@npm:^12.0.6 → npm:12.16.0
      ├─ react-d3-tree@npm:^3.6.4 → npm:3.6.6
      ├─ react-diff-viewer-continued@npm:^4.0.5 → npm:4.0.6
      ├─ react-hotkeys-hook@npm:^4.6.1 → npm:4.6.2
      ├─ react-tooltip@npm:^5.28.0 → npm:5.28.1
      └─ tailwind-merge@npm:^3.0.1 → npm:3.3.0
Dominant language
TypeScript
Stars
975
Forks
55
PR merge metrics
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from code-forge-io/react-router-devtools

All issues in code-forge-io/react-router-devtools

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.