Expose the Captun worker as a package subpath

[mmkal]

Summary

Expose the existing Captun Worker entrypoint as a package subpath. Published consumers can now import captun/worker and get the default Worker handler plus the CaptunServerShard Durable Object class from the compiled package.

Intended effect

Downstream Cloudflare stacks can deploy Captun inside their own app instead of depending on a separate Captun deployment or threading custom egress fetch hooks through tests:

import worker, { CaptunServerShard } from "captun/worker";

export { CaptunServerShard };
export default worker;

The source export points to src/worker.ts for repo-local usage, and the publish export points to dist/worker.js/dist/worker.d.ts so packed and published packages expose the same subpath.

Verification

• pnpm check
• pnpm test
• pnpm pack --pack-destination ignoreme-pack
• tar -xOf ignoreme-pack/captun-0.0.2.tgz package/package.json confirmed ./worker maps to ./dist/worker.js and ./dist/worker.d.ts.
• pnpm publish:dry-run ran check, test, and prepack, then completed successfully for captun@0.0.2.

---

Note

Low Risk
Low risk packaging/type-surface change that primarily affects how consumers import the Worker; minimal runtime logic changes beyond the env type definition.

Overview
Exposes the existing Worker entrypoint as a new captun/worker package subpath for both source usage and published builds, mapping to src/worker.ts and dist/worker.* respectively.

Updates src/worker.ts to define its own CaptunEnv shape (including the CaptunServerShard DO namespace) instead of extending a repo-local Env type, improving portability of the generated .d.ts for downstream deployments.

^{Reviewed by Cursor Bugbot for commit 5f1a8f4. Bugbot is set up for automated code reviews on this repo. Configure here.}

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/captun@14

commit: 5f1a8f4