SvelteKitError: Not found: /.well-known/appspecific/com.chrome.devtools.json

Describe the bug

I'm suddently getting this in my terminal during dev mode. No idea what's caused it or whether it's actually impacting anything. I am reading a value from localStorage in my root +layout.json file, but that's the only interaction with localstorage in the app, other than setting that value on user sign in.

Best of luck...

SvelteKitError: Not found: /.well-known/appspecific/com.chrome.devtools.json
at resolve (C:\devprojects\learning\pwa-ktt\node_modules@sveltejs\kit\src\runtime\server\respond.js:582:13)
at C:\devprojects\learning\pwa-ktt\node_modules@sveltejs\kit\src\runtime\server\respond.js:370:7
at AsyncLocalStorage.run (node:internal/async_local_storage/async_hooks:91:14)
at with_event (C:\devprojects\learning\pwa-ktt\node_modules@sveltejs\kit\src\runtime\app\server\event.js:49:20)
at resolve (C:\devprojects\learning\pwa-ktt\node_modules@sveltejs\kit\src\runtime\server\respond.js:369:6)
at init_promise.#options.hooks.handle (C:\devprojects\learning\pwa-ktt\node_modules@sveltejs\kit\src\runtime\server\index.js:76:56)
at C:\devprojects\learning\pwa-ktt\node_modules@sveltejs\kit\src\runtime\server\respond.js:364:18
at AsyncLocalStorage.run (node:internal/async_local_storage/async_hooks:91:14)
at with_event (C:\devprojects\learning\pwa-ktt\node_modules@sveltejs\kit\src\runtime\app\server\event.js:49:20)
at respond (C:\devprojects\learning\pwa-ktt\node_modules@sveltejs\kit\src\runtime\server\respond.js:363:26) {
status: 404,
text: 'Not Found'
}

Reproduction

I wouldn't now how to provide a reproduction for this other than providing my actual repo, because I don't know what originally caused this issue.

Logs

System Info

System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 13th Gen Intel(R) Core(TM) i5-1345U
    Memory: 18.01 GB / 31.66 GB
  Binaries:
    Node: 22.13.1 - C:\nvm4w\nodejs\node.EXE
    npm: 10.9.2 - C:\nvm4w\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (129.0.2792.89)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    @sveltejs/adapter-auto: ^4.0.0 => 4.0.0 
    @sveltejs/kit: ^2.16.0 => 2.20.3 
    @sveltejs/vite-plugin-svelte: ^5.0.0 => 5.0.3 
    svelte: ^5.0.0 => 5.25.6 
    vite: ^6.0.0 => 6.2.4

Severity

annoyance

Additional Information

No response

Sounds like Chrome dev tools making these requests - https://goo.gle/devtools-json-design - which would mean there's nothing for us to fix.

Related:
https://www.reddit.com/r/node/comments/1kcr0wh/odd_request_coming_into_my_localhost_server_from/

To suppress with hooks:

// hooks.server.ts
import type { Handle } from '@sveltejs/kit';

export const handle: Handle = async ({ event, resolve }) => {

	if (
		event.url.pathname.startsWith(
			'/.well-known/appspecific/com.chrome.devtools'
		)
	) {
		return new Response(null, { status: 204 }); // Return empty response with 204 No Content
	}

return await resolve(event);

};

Or create the file according to
https://chromium.googlesource.com/devtools/devtools-frontend/+/main/docs/ecosystem/automatic_workspace_folders.md

I had to create it in static for it to work.

@benquan

In addition to the suggestions provided above by @benquan I noticed at the bottom of the page he linked it mentions a vite plugin that also does the trick.

This feature allows you to use workspaces in Chrome DevTools so you can save changes to local files from the DevTools window.

I'm uninstalling my current IDE, and DevTools will be my new main, who's with me ;)

@benquan

As mentioned in the Reddit link shared by @benquan:

It’s a request made by Chrome DevTools itself as part of this feature: https://chromium.googlesource.com/devtools/devtools-frontend/+/main/docs/ecosystem/automatic_workspace_folders.md.

I was able to resolve the issue by navigating to chrome://flags and disabling the DevTools Project Settings. I also disabled DevTools Automatic Workspace Folders since it’s closely related.

@srt1104

@srt1104 Thank you, Btw is it going to be a problem in future ?

feat: bump vite to resolve sveltejs/kit#13743

I'm still getting this error with sveltekit 2.21.0 and vite 6.3.5, should i wait for the next sveltekit version?
I'm gonna disable the setting in chrome for now.

Also still getting it with vite 6.3.5

…

On Wed, May 14, 2025 at 9:05 PM anxpara ***@***.***> wrote: *anxpara* left a comment (sveltejs/kit#13743) <#13743 (comment)> I'm still getting this error with sveltekit 2.21.0 and vite 6.3.5, should i wait for the next sveltekit version? I'm gonna disable the setting in chrome for now. — Reply to this email directly, view it on GitHub <#13743 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACH3QI2CLUXF4AA3LZGMOP326OHZJAVCNFSM6AAAAAB35NDNK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBRGI2TEMJRGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

same problem

Given how prevalent this is (I encounter it constantly) and how annoying it is, I think it would be reasonable to do something about it, even if that's just suppressing errors in dev to prevent console spam

I'm using the Brave browser, and the terminal keeps prompting this error, and it's hard to see the other error messages that I need.

First

npm install -D vite-plugin-devtools-json

Then in the vite configuration,vite.config.ts

import { sveltekit } from "@sveltejs/kit/vite";
import { defineConfig } from "vite";
import devtoolsJson from "vite-plugin-devtools-json";
export default defineConfig({
  plugins: [sveltekit(),devtoolsJson()],
});

This caused an issue where a param from my page.params changed when the browser attempted to go to /.well-known/appspecific/com.chrome.devtools.json and then re-triggered my layout load function, which then was missing the page.params from that url, and created a mess. I disabled the chrome settings and then it was fine, but caused a lot of troubleshooting trying to change code to see why my params were being reset. I don't recall seeing this issue before, and it's been some months since I worked on this project, so seems something changed, but it would be nice if Sveltekit prevented this. From the AI

DevTools Request: Almost immediately after, your browser's DevTools (a common feature in Chrome) makes a background request for a resource at /.well-known/appspecific/com.chrome.devtools.json. This is an internal request and has nothing to do with your application's pages.
Layout Reload: Because you have a universal load function in your root layout (src/routes/+layout.server.js), SvelteKit runs it for this DevTools request.
Params Reset: For this request, the URL doesn't match your playlist route, so params is an empty object ({}). Your load function sees no params.playlist, defaults to an empty playlist, and returns that.
UI Update: SvelteKit sees this new data from the load function and updates your page, causing page.params.playlist to become undefined and the playlist data to be replaced with the empty placeholder.

@half-metal

@half-metal this is Chrome deciding everyone wants random requests to a random route in their project, without opt-in. Would recommend joining the chorus asking them to please stop.

Navigation Menu

Repository navigation

SvelteKitError: Not found: /.well-known/appspecific/com.chrome.devtools.json #13743

Describe the bug

Reproduction

Logs

System Info

Severity

Additional Information

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

SvelteKitError: Not found: /.well-known/appspecific/com.chrome.devtools.json #13743

Description

Describe the bug

Reproduction

Logs

System Info

Severity

Additional Information

Activity

Conduitry commented on Apr 26, 2025

benquan commented on May 4, 2025

groundbirdaircat commented on May 9, 2025

srt1104 commented on May 9, 2025

ImalKesara commented on May 11, 2025

serranocirrus commented on May 14, 2025

ianengelbrecht commented on May 14, 2025

applemate commented on May 21, 2025

Rich-Harris commented on May 26, 2025

dufu1991 commented on May 27, 2025

VCCICCV commented on May 29, 2025

half-metal commented on Jun 9, 2025

elliott-with-the-longest-name-on-github commented on Jun 9, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions