Distribution Wave 0: publish the developer packages to npm

Radin committed …

⧉c573e9b4071b

Author

Radin · radin@coline.appAug 10, 2026 at 22:41

Committer

Radin · radin@coline.appAug 10, 2026 at 22:41

Parents

122b9e1a995d

Distribution Wave 0: publish the developer packages to npm

All four packages are live on the public registry under MIT:

- @colineapp/sdk@0.2.0 — tsup ESM build + full .d.ts; exports ./v2 and
  ./testing. publishConfig.exports points npm consumers at dist while
  the monorepo keeps importing TypeScript source directly.
- @colineapp/app-runtime@0.2.0 — the sandbox bridge.
- @colineapp/ui@0.2.0 — components with a 'use client' banner, peer
  react 19, and dist/styles.css shipped in the tarball.
- create-coline-app@2.0.0 — bin shims + templates; the backendless
  template now pins published ranges (@colineapp/sdk ^0.2.0).

Pipeline: scripts/publish-packages.sh (pnpm packages:publish) builds,
packs with pnpm (workspace:^ deps rewrite to real semver; exports
override applies), skips versions already on the registry, and
publishes with npm's browser 2FA flow — npm hard-requires account 2FA
for publishing now.

Verified from the live registry as a stranger would: npx
create-coline-app → npm install → npm test green → tsc clean; plus
@colineapp/ui import + styles.css and app-runtime import in a bare
project. Each package ships README + LICENSE; the sdk's internal-notes
README moved to INTERNAL.md and was replaced with a real quickstart.

The /developers/docs 'npx create-coline-app my-app' quickstart is now
literally true for anyone on the internet.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>