Skip to content
TheChatArchiveThe Chat Archive
DeepSeekdeepseek-v3-0324· DeepSeekHugging Face LMArena Human Preference 140K

Using SvelteKit. pnpm run dev caused this error, but it seems to be working in the…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Coherecommand-a-03-2025’s answer.
  1. User

    Using SvelteKit. pnpm run dev caused this error, but it seems to be working in the browser.

    SvelteKitError: Not found: /.well-known/appspecific/com.chrome.devtools.json
        at resolve (D:\developer\code\dev\node_modules\.pnpm\@sveltejs+kit@2.20.4_@svelt_70352feefd55761519f3694304fe42f5\node_modules\@sveltejs\kit\src\runtime\server\respond.js:582:13)
        at D:\developer\code\dev\node_modules\.pnpm\@sveltejs+kit@2.20.4_@svelt_70352feefd55761519f3694304fe42f5\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 (D:\developer\code\dev\node_modules\.pnpm\@sveltejs+kit@2.20.4_@svelt_70352feefd55761519f3694304fe42f5\node_modules\@sveltejs\kit\src\runtime\app\server\event.js:49:20)
        at resolve (D:\developer\code\dev\node_modules\.pnpm\@sveltejs+kit@2.20.4_@svelt_70352feefd55761519f3694304fe42f5\node_modules\@sveltejs\kit\src\runtime\server\respond.js:369:6)
        at init_promise.#options.hooks.handle (D:\developer\code\dev\node_modules\.pnpm\@sveltejs+kit@2.20.4_@svelt_70352feefd55761519f3694304fe42f5\node_modules\@sveltejs\kit\src\runtime\server\index.js:76:56) 
        at D:\developer\code\dev\node_modules\.pnpm\@sveltejs+kit@2.20.4_@svelt_70352feefd55761519f3694304fe42f5\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 (D:\developer\code\dev\node_modules\.pnpm\@sveltejs+kit@2.20.4_@svelt_70352feefd55761519f3694304fe42f5\node_modules\@sveltejs\kit\src\runtime\app\server\event.js:49:20)
        at respond (D:\developer\code\dev\node_modules\.pnpm\@sveltejs+kit@2.20.4_@svelt_70352feefd55761519f3694304fe42f5\node_modules\@sveltejs\kit\src\runtime\server\respond.js:363:26) {
      status: 404,
      text: 'Not Found'
    }
    
  2. DeepSeek Assistant

    This error occurs because Chrome DevTools is trying to access a specific file (.well-known/appspecific/com.chrome.devtools.json) that doesn't exist in your SvelteKit project. This is a harmless error and doesn't affect your application's functionality, but it can be annoying in the console.

    Solutions

    1. Ignore the error (recommended)

    Since this is just a Chrome DevTools request and doesn't affect your app, you can safely ignore it. Your app is still working fine in the browser.

    2. Create a route to handle the request

    If you want to suppress the error, you can create a route that responds to this request:

    1. Create a new file at src/routes/.well-known/appspecific/com.chrome.devtools.json/+server.js:
    export function GET() {
        return new Response(JSON.stringify({}), {
            headers: {
                'Content-Type': 'application/json'
            }
        });
    }
    
    1. Or if you prefer a static response, create src/routes/.well-known/appspecific/com.chrome.devtools.json/+server.ts:
    import { json } from '@sveltejs/kit';
    
    export function GET() {
        return json({});
    }
    

    3. Handle it in your hooks

    Alternatively, you can handle this in your server hooks:

    // src/hooks.server.js
    export async function handle({ event, resolve }) {
        if (event.url.pathname === '/.well-known/appspecific/com.chrome.devtools.json') {
            return new Response(JSON.stringify({}), {
                headers: {
                    'Content-Type': 'application/json'
                }
            });
        }
    
        return resolve(event);
    }
    

    Why this happens

    Chrome DevTools occasionally makes requests to this endpoint to check for developer-specific configurations. Since your SvelteKit app doesn't have this file, it returns a 404, which is logged as an error in your console.

    The simplest solution is to just ignore it, but if the error messages bother you, implementing one of the solutions above will make them go away.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.