Skip to content

feat: make bip-kit an installable package - #1

Merged
catomean merged 1 commit into
mainfrom
feat/publishable-package
Aug 20, 2026
Merged

feat: make bip-kit an installable package#1
catomean merged 1 commit into
mainfrom
feat/publishable-package

Conversation

@catomean

Copy link
Copy Markdown
Collaborator

Turns the scaffold into a real, publishable package:

  • Package shape: single unscoped bip-kit, tsc → dist/, exports map with types, files allowlist, provenance. NodeNext resolution with explicit .js specifiers.
  • 32 real tests (the old gate ran zero): parser block semantics (CRLF, unterminated fences, table/paragraph ambiguity, embeds), frontmatter quoting, video allowlist rejections incl. lookalike hosts, and a tarball-consumer test that imports the packed package by bare specifier.
  • CI + reconciler publish: merging a version bump to main is the release; publish auth is npm trusted publishing (OIDC) — no token anywhere.
  • README as GTM: rewritten around the content contract; the cp-sync model is gone — FleetCrown and AOZ will depend on the npm package next.

First publish note: npm can't pin a trusted publisher on a package that doesn't exist yet, so 0.1.0 ships once via one-time auth; every release after is tokenless.

🤖 Generated with Claude Code

- Single unscoped package `bip-kit` (was @bip-kit/core in a workspace):
  tsc build to dist/, exports map with types, files allowlist, provenance.
- NodeNext module resolution with explicit .js specifiers.
- Real test suite (32 tests): parser block semantics incl. CRLF, unterminated
  fences, table/paragraph ambiguity, embed allowlisting; frontmatter quoting
  and colon-in-value; video allowlist rejections incl. lookalike hosts; and a
  tarball-consumer test that imports the packed package by bare specifier so
  the exports map and files list are what gets tested, not relative paths.
- CI (verify) + reconciler publish workflow: merging a version bump to main
  is the release; auth is npm trusted publishing (OIDC), no token anywhere.
- README rewritten around the content contract; templates now reference
  `bip-kit`. The cp-based "sync from studio" model is gone: FleetCrown and
  AOZ will consume this package from npm instead of vendored copies.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@catomean
catomean merged commit 24a5506 into main Aug 20, 2026
1 check passed
@catomean
catomean deleted the feat/publishable-package branch August 20, 2026 23:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant