fix(bundle): resolution fixes

[aryasaatvik]

Two fixes to what the bundler resolves.

cloudflare:workers is supplied by workerd and has no filesystem existence, but rolldown resolves imports before tree-shaking — so any bundled graph referencing it fails with [UNRESOLVED_IMPORT] even where a runtime guard makes the import dead code. The CLI's dev executable reaches cloudflare_workers.ts (whose guarded import("cloudflare:workers") falls back to a stub off workerd), and a cross-provider Lambda can reach it too — a Lambda can never resolve the module, so keeping it external lets the runtime fallback handle it. Worker bundles already get this from the cloudflare rolldown plugin.

  defineConfig({
    entry: ["bin/exec.ts"],
+   external: ["cloudflare:workers"],

Alchemy's SDK dependencies (@distilled.cloud/*) resolve from alchemy's own installation instead of the consumer's package graph, which only worked when the package manager happened to hoist them:

const selfResolvePlugin = (): rolldown.Plugin => ({
  name: "alchemy:self-resolve",
  resolveId: {
    filter: { id: /^@distilled\.cloud\// },
    handler(source) {
      try {
        return fileURLToPath(import.meta.resolve(source));
      } catch {
        return null;
      }
    },
  },
});

Peers like Effect are deliberately not handled — they must resolve from the consumer so the runtime has a single Effect identity. An id alchemy's own install cannot resolve falls through to normal resolution.

[sam-goodwin]

This makes sense

[sam-goodwin]

These are not all private. All the distilled SDKs are in there. What motivated this?

[aryasaatvik]

Fair — "private" is the wrong word; they're published. The intent is provenance, not privacy: resolve @distilled.cloud/* from alchemy's own install rather than the consumer's package graph.

What motivated it: I consume alchemy in another monorepo from a packed tarball built off a worktree carrying my open PRs plus distilled patches that aren't on npm yet. (bun link isn't workable there — linking pulls alchemy's whole source tree into the dev server's watch graph, >10k files, and the process hits the macOS open-file limit.) The patched SDK builds ride inside alchemy's install, so bundled user code has to resolve @distilled.cloud/* to those copies — the consumer graph either doesn't have them or hoists the unpatched registry versions.

It's not specific to that workflow though: imports reached from the virtual entry have no importer path, so without the plugin resolution falls back to the consumer graph and only works when the package manager happens to hoist — and the versions it hoists aren't necessarily the ones alchemy's install was built against.