[fix] prevent unused types warning

[dummdidumm]

Fixes #6290

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. All changesets should be patch until SvelteKit 1.0

[changeset-bot]

🦋 Changeset detected

Latest commit: 140b849

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

[dummdidumm]

Just realized it's also benefitial to add a ts-nocheck comment at the top of all of these, so in case there are type errors they don't show up twice. Will do that tomorrow on this PR.

[Rich-Harris]

hahaha this is an incredible solution — i was thinking about walking the AST to see if the import type declaration was unused so we could remove it altogether. real 'the russians used a pencil' energy

[Rich-Harris]

rescinding my approval, but only so i don't accidentally merge it before the no-check stuff gets added

[benmccann]

This really does feel like we need type tests 😄 I don't know that we need to hold this up for tests since there's so much on our plates right now, but it might be nice to do post-summit

[dummdidumm]

I agree we need type tests, but this one isn't really related to that. It's a hidden file generated from the user's file, and there are already tests for it.

[benmccann]

Ah, I missed that there's a test because it was in the src die and I'm so used to all our tests being integration tests. Thanks for correcting me!