Spamming 404 Requests on Chromium browsers in dev server

[b-bot]

When in dev mode on Next.js the thirdweb package is making hundreds of requests to file routes that don't exist all returning 404 on Chromium browsers like Chrome and Edge. Not happening in Safari for example.

I believe this is related to the new dev tools: https://chromium.googlesource.com/devtools/devtools-frontend/+/main/docs/ecosystem/automatic_workspace_folders.md

I was getting it before with one single file request as per this reddit article: https://www.reddit.com/r/node/comments/1kcr0wh/odd_request_coming_into_my_localhost_server_from/
GET /.well-known/appspecific/com.chrome.devtools.json 404

In fact it always hits this route before the other routes start going crazy.

Not sure when it started happening, don't think it was a specific version of thirdweb rather a browser update. I would simply silence logs but it actually hits performance. It might be the way the in app wallet is mounted as a seperate app.

Importantly it doesn't seem to happen once deployed to Vercel, well not yet anyways.

Any advice on how to proceed? This is a big problem and makes my dev server constantly refresh breaking hot reload.

[linear]

TOOL-4458 Spamming 404 Requests on Chromium borwsers in dev server

[github-actions]

This issue has been inactive for 7 days. It is now marked as stale and will be closed in 2 days if no further activity occurs.

[b-bot]

Doing this in my next config for now:

  logging: {
    incomingRequests: false,
  },

But DX is terrible because of this.

[jnsdls]

Doing this in my next config for now:

  logging: {
    incomingRequests: false,
  },

But DX is terrible because of this.

hey @b-bot, could you share your full next config file as well as next versions etc - IDEALLY a reproduction case that exhibits this issue, I'm not able to reproduce it so far

[github-actions]

This issue has been inactive for 7 days. It is now marked as stale and will be closed in 2 days if no further activity occurs.