Skip to content

Chromium DevTools well-known request still logs noisy route miss in framework mode #15337

Open

Description

@ahammednibras8

I'm using React Router as a...

framework

Reproduction

When running a React Router framework app on localhost and opening the app in Chrome/Chromium, Chrome DevTools requests:

/.well-known/appspecific/com.chrome.devtools.json

React Router handles this like an application document request and logs/throws:

Error: No route matches URL "/.well-known/appspecific/com.chrome.devtools.json"

This is related to Chromium DevTools Automatic Workspace Folders. Chromium documents that DevTools requests com.chrome.devtools.json from /.well-known/appspecific/ on localhost:

https://chromium.googlesource.com/devtools/devtools-frontend/+/main/docs/ecosystem/automatic_workspace_folders.md

There is a prior issue for this, #13516, but it is closed. I am opening this because it still reproduces on current React Router 8 framework usage, and the current workaround still requires every app to add its own route/static handler for a browser/devtools-owned path.

A route-level workaround works:

route(".well-known/appspecific/com.chrome.devtools.json", "routes/chrome-devtools.ts")
export function loader() {
  return new Response(null, {
    status: 204,
    headers: {
      "Cache-Control": "no-store",
    },
  });
}

But this feels like dev-server/framework noise rather than application behavior.

System Info

System:
  OS: macOS 26.5.1
  Package manager: pnpm 11.13.1
  Node: v26.4.0 during local check; project engine is >=24.18.0 <25

npmPackages:
  @react-router/dev: 8.2.0
  @react-router/node: 8.2.0
  @react-router/serve: 8.2.0
  react-router: 8.2.0
  vite: 8.1.5

Used Package Manager

pnpm

Expected Behavior

Chrome DevTools' localhost-only well-known request should not create noisy React Router route-miss errors in the app logs.

Possible acceptable outcomes:

  1. React Router dev/framework server quietly returns 204 No Content for this exact path in dev/local mode.
  2. React Router documents the recommended workaround.
  3. React Router exposes a small documented hook/config point for ignoring well-known devtools requests before app route matching.

I do not think React Router should necessarily generate a real com.chrome.devtools.json containing local absolute paths by default. A quiet 204/documented handling path would be enough to remove confusing noise.

Actual Behavior

React Router reports:

Error: No route matches URL "/.well-known/appspecific/com.chrome.devtools.json"

This is confusing because the request is not from app navigation and not from user code; it is Chrome DevTools probing localhost.

Activity

  1. Bhaskar-tech1 commented on Nov 21, 2026

    @Bhaskar-tech1

    Hi! I'd like to contribute to this issue.

    I've reviewed the reproduction and understand that Chromium DevTools' automatic localhost request is currently being treated as a normal application document request, resulting in unnecessary route-miss errors.

    I'd like to investigate the framework-mode request handling in @react-router/dev and explore a minimal development-only solution, with regression tests covering this well-known path and normal application routing.

    I also noticed the reference to the earlier issue #13516. I'll review its previous resolution to ensure the proposed fix doesn't duplicate existing behavior.

    Would this issue be open for community contributions?

    Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions