fix: suppress console spam for chrome devtools requests

[Rich-Harris]

Closes #13743. As an alternative, we might consider responding with some data (which is the intended behaviour), but I'm not familiar with it and we would need to think through any security implications or whatever

---

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Edits

• Please ensure that 'Allow edits from maintainers' is checked. PRs without this option may be closed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 803ce3a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@sveltejs/kit	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[svelte-docs-bot]

Preview: https://svelte-dev-git-preview-kit-13830-svelte.vercel.app/

[Rich-Harris]

could always delegate to https://github.com/ChromeDevTools/vite-plugin-devtools-json

[benmccann]

I sent vitejs/awesome-vite#1030 to make it easier to find again if we need to track it down

[benmccann]

I don't think we need to add a TODO. I'm not sure I really need Chrome acting as an editor. lgtm other than that though

[Rich-Harris]

I just tried adding the plugin and it is pretty useful. The plugin is extremely straightforward. I'm tempted to integrate it. Is there any real reason not to?

[benmccann]

Maybe I should give it a try. What did you find useful about it?

[benmccann]

Ah, I hadn't checked Discord yet. Will take a look there

[MathiasWP]

Not sure where to post this, but i just got an unexpected error in my page load method, and the reason was that .well-known, appspecific and com.chrome.devtools.json came in as params in my load method.

I have this load function:

export const load: PageLoad = async function ({ parent, params }) {
	const { githubClient } = await parent();
	const { owner, repo, provider } = params;

	async function getData() {
		const [pullRequests, user] = await Promise.all([
			githubClient.getPullRequests(owner, repo),
			githubClient.getAuthenticatedUser()
		]);

		return {
			pullRequests,
			user
		};
	}

	return {
		streamed: {
			data: getData()
		},
		owner,
		repo,
		provider
	};
};

And for some reason provider in my params was .well-known, owner was appspecific and repo was com.chrome.devtools.json.

Update: It seems that adding https://github.com/ChromeDevTools/vite-plugin-devtools-json fixed it

[Rich-Harris]

please open a new issue

[MathiasWP]

please open a new issue

#13863