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

ianengelbrecht · 2025-04-26T13:23:54Z

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

Conduitry · 2025-04-26T13:45:12Z

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

benquan · 2025-05-04T12:32:53Z

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.

groundbirdaircat · 2025-05-09T02:12:33Z

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 ;)

srt1104 · 2025-05-09T05:57:22Z

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.

ImalKesara · 2025-05-11T19:16:43Z

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

anxpara · 2025-05-14T19:05:34Z

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.

ianengelbrecht · 2025-05-14T20:25:47Z

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: ***@***.***>

xgwang-scienceos · 2025-05-15T04:37:58Z

Thanks for the flag disable solution: @srt1104

One caveat: I had to restart chrome after disabling flags for it to work

applemate · 2025-05-21T14:44:06Z

same problem

Rich-Harris · 2025-05-26T15:23:36Z

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

dufu1991 · 2025-05-27T01:27:02Z

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.

VCCICCV · 2025-05-29T04:16:13Z

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()],
});

Conduitry closed this as not planned Won't fix, can't repro, duplicate, stale Apr 26, 2025

Conduitry mentioned this issue May 6, 2025

Error message in console from dev server while using Brave sveltejs/svelte#15875

Closed

Conduitry marked this as a duplicate of sveltejs/svelte#15875 May 6, 2025

peterpeterparker added a commit to peterpeterparker/papyrs-wip that referenced this issue May 12, 2025

feat: bump vite to resolve sveltejs/kit#13743

55a1a17

Rich-Harris reopened this May 26, 2025

Rich-Harris linked a pull request May 26, 2025 that will close this issue

fix: suppress console spam for chrome devtools requests #13830

Open

6 tasks

sellerscrisp mentioned this issue May 27, 2025

[404] /.well-known/appspecific/com.chrome.devtools.json withastro/astro#13789

Open

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

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

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

ianengelbrecht commented Apr 26, 2025

Conduitry commented Apr 26, 2025 •

edited

Loading

Uh oh!

benquan commented May 4, 2025

Uh oh!

groundbirdaircat commented May 9, 2025

Uh oh!

srt1104 commented May 9, 2025

Uh oh!

ImalKesara commented May 11, 2025

Uh oh!

anxpara commented May 14, 2025

Uh oh!

ianengelbrecht commented May 14, 2025 via email

Uh oh!

xgwang-scienceos commented May 15, 2025

Uh oh!

applemate commented May 21, 2025

Uh oh!

Rich-Harris commented May 26, 2025

Uh oh!

dufu1991 commented May 27, 2025

Uh oh!

VCCICCV commented May 29, 2025

Uh oh!

Uh oh!

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

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

Comments

ianengelbrecht commented Apr 26, 2025

Describe the bug

Reproduction

Logs

System Info

Severity

Additional Information

Conduitry commented Apr 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

benquan commented May 4, 2025

Uh oh!

groundbirdaircat commented May 9, 2025

Uh oh!

srt1104 commented May 9, 2025

Uh oh!

ImalKesara commented May 11, 2025

Uh oh!

anxpara commented May 14, 2025

Uh oh!

ianengelbrecht commented May 14, 2025 via email

Uh oh!

xgwang-scienceos commented May 15, 2025

Uh oh!

applemate commented May 21, 2025

Uh oh!

Rich-Harris commented May 26, 2025

Uh oh!

dufu1991 commented May 27, 2025

Uh oh!

VCCICCV commented May 29, 2025

Uh oh!

Conduitry commented Apr 26, 2025 •

edited

Loading