chore: use pkg.imports for builder.js

[Rich-Harris]

Occurs to me that for modules that are used throughout the codebase, like builders.js, we could use pkg.imports and save ourselves a lot of ../../../

Might need to update the resolution logic in the playground but we ought to do that anyway. Can anyone think of a reason not to do this?

[changeset-bot]

⚠️ No Changeset found

Latest commit: c192585

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

[github-actions]

Playground

pnpm add https://pkg.pr.new/svelte@15785

[Rich-Harris]

Actually it looks like the playground already works, because it's using the bundled compiler

[svelte-docs-bot]

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

[dummdidumm]

We should double check that (our) rollup and webpack (plugins) work with it but otherwise I see no reason not to do this

[Rich-Harris]

Confirmed it works with both rollup and webpack

[Rich-Harris]

I'll take #15785 (comment) as a verbal approval and merge this so that it doesn't become a merge conflict magnet. Once we've established that the release works as expected we can apply the same treatment to other common modules. This will clean up a bunch of stuff