fix: consistently use bare import for internals

[Rich-Harris]

In #14447 I broke a cardinal rule — code in src/runtime should only ever import code from src/exports via the public bare imports made available via pkg.exports. Otherwise, there's a danger that a given module will be loaded through both Vite and Node, causing breakage.

I ignored that rule because I was trying to deal with some tricky resolution bug, and #14505 was my reward. Luckily I think the tricky resolution bug is solved by not having a nested pkg.exports map, and instead abusing pkg.imports to achieve the intended outcome.

This is one of those things that's extremely hard to test for from within the workspace, because of how Vite works. But I think this solution is good. Closes #14505.

---

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: 6467e0f

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

[Rich-Harris]

(Tested the repro in #14505 with the pkg.pr.new version from this PR, and it does indeed appear to be fixed)

[teemingc]

What's the reason for this import not using the import map $apps/paths/internal/server instead? Does the rule only apply to internal paths using the export map?