Skip to content

Add a workaround for Chrome's DevTools standard settings #709

@Harriethw

Description

@Harriethw

When trying to setup routing logic in app/routes.js, I was getting the error:

Error: Page not found: /.well-known/appspecific/com.chrome.devtools.json

This is related to Chrome's Dev Tools due to a change in 2025 . It looks like it should be possible to suppress this by disabling dev tools at chrome://flags/#devtools-project-settings and restarting, but this didn't work for me locally.

As this is a prototype kit for use by non-technical people it might be easier to include the below workaround by default. It has already been
implemented in use cases in NHSDigital.

// app/routes.js
// Workaround for Chrome DevTools requesting a specific URL
router.get('/.well-known/appspecific/com.chrome.devtools.json', (_req, res) => {
  // Either return an empty JSON object
  res.json({})
  // Or send a 204 No Content response
  // res.status(204).end();
})

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions