Add support for Chrome DevTools Workspaces #5716

Activity

1. aakritee11 commented on Oct 19, 2026

   

   aakritee11

   on Oct 19, 2026

   More actions

   Hi! I'd like to work on this. Could you assign it to me?

   I built a working prototype in a test project using setupMiddlewares: Chrome connects to the project automatically, and edits made in DevTools save to disk.

   My plan for the PR:

   1. Add a devServer option (disabled by default, as you said).
   2. When enabled, serve /.well-known/appspecific/com.chrome.devtools.json with the project root and a persisted UUID.
   3. Add tests and a docs entry.

   Questions before I start:

   • What should the option be called?
   • Should the endpoint only respond on localhost, since it exposes the absolute project path?

   Happy to adjust the approach based on your feedback.
2. AnumanyaJaiswal commented on Oct 26, 2026

   

   AnumanyaJaiswal

   on Oct 26, 2026

   More actions

   Hi! I’d like to work on this if it’s still available. I’ve been reading through setupMiddlewares() and how options are validated and registered in webpack-dev-server.

   My proposed implementation approach is:

   1. Add an opt-in configuration option

   Add a new devServer option, to control whether Chrome DevTools Workspaces integration is enabled.

   

   2. Disable it by default

   

   3. Implement the discovery endpoint

   When enabled, serve /.well-known/appspecific/com.chrome.devtools.json with the workspace metadata in the format expected by Chrome DevTools.

   For example, the workspace metadata could be constructed along these lines:

   import { randomUUID } from "node:crypto";
   
   const workspace = {
     uuid: randomUUID(),
     root: /* absolute project root */,
   };

   The endpoint would return a JSON response containing this workspace configuration. I’ll verify the exact response schema and UUID requirements against Chrome’s documentation before implementing it.

   4. Add tests

   Test that the endpoint is unavailable when the option is disabled and returns the expected response when enabled.

   5. Update documentation

   Document the new option, its default behavior, and how to enable the integration.

   @aakritee11 , I saw you mentioned prototyping this. I’d be happy to coordinate or split the work if you’re already working on the implementation.

   @bjohansebas , kindly assign this issue to me if it’s still available? I’m happy to adjust the option name or implementation based on your feedback before opening a PR.