refactor: migrate to exsolve for module resolution

[pi0]

This PR migrates import-meta-resolve to unjs/exsolve which is actively maintained and has features such as global cache to improve performance.

Note: exsolve utils default to resolving from CWD which I noticed was the case for both usages here.

---

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]

⚠️ No Changeset found

Latest commit: e7f9725

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[svelte-docs-bot]

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

[pi0]

we could use { try: true } here also to avoid try/catch situation, however I didn't want to make too much changes.

[benmccann]

This code is simpler, which is nice. I don't understand why that is and if we're deviating more from the import.meta.resolve API.

I think we'd drop either library as a dependency in SvelteKit 3 (#13528)

[Rich-Harris]

Thank you. I would prefer to keep things as they are, since when we're able to switch to import.meta.resolve it'll be easier that way, and there's no benefit to switching in the meantime (the caching isn't something that would benefit us, given how we're using it). The reason import-meta-resolve isn't 'actively maintained' is that it's done — it has no open issues or PRs, and fulfils its goal of ponyfilling import.meta.resolve.

[pi0]

Totally fine if you like to keep things as is, I just wanted to offer a better option n in meantime (it is simpler usage and 20kb less install size I found a reason to make PR while was inspecting svelte-kit install size).

Also, a note might be worth considering, Usage of import.meta.resolve(<id>, <cwd>) is not allowed in deno (by 2.2.2 at least), it is a gray area in Bun also I think was considered to be dropped (since Node.js support is also experimental for second arg)