Compatibility And Publication

Use this page before copying install commands into a new app. It answers one question: should the host depend on a published package, or on the sibling local package in this workspace?

These docs target Mika 0.2.0, including WebMCP, optional ChatGPT annotations, and the breaking ordinary Astro Action result envelope. The local source package metadata declares @bnomei/emdash-mika version 0.2.0; this release is not yet published. The sibling seeded template uses file:../emdash-mika and rebuilds the local package before dev, build, preview, typecheck, test, and seed commands.

Treat registry availability as a release-time check, not a docs constant. Use the registry path for these features only after the 0.2.0 release is published and its peer ranges match the host. See Browser Shopping Tools and Action result migration.

Source-Of-Truth Ranges

../emdash-mika/package.json is authoritative for package metadata:

Surface	Current source value
Package name	@bnomei/emdash-mika
Local package version	0.2.0 (unpublished)
Node engine	^22.18.0 || ^24.11.0 || >=26.0.0
Astro peer	^7.3.8
EmDash peer	^1.2.0
React / React DOM peers (optional)	^19.3.0
Stripe peer (optional)	^23.0.0
Kumo peer (optional)	^2.6.0
Published file set	dist and src/templates
Copyable template export	./templates/astro/*

The seeded GitHub template depends on Mika through file:../emdash-mika; its runtime must satisfy Mika’s engine and peer ranges. Check the template’s own package.json for any additional constraints rather than reusing an older Node or EmDash baseline.

The package development toolchain retains TypeScript 6.0.3 for checker support and uses vite-plus 1.1.0 and Kysely 0.29.6. These are not additional host peer requirements. Kumo development uses 2.14.0, while its ^2.6.0 peer range also permits the Cloudflare host’s exact 2.6.0 pin; do not treat the development version as the minimum supported UI version.

Install Mode

Local workspace

Use this mode while Mika is unpublished or while developing the sibling repos together.

The seeded template already depends on Mika with file:../emdash-mika and rebuilds the package during its lifecycle scripts. Run it from Quickstart: Seeded Template.

In a separate host app, point the dependency at the sibling package until a public version exists:

{
  "dependencies": {
    "@bnomei/emdash-mika": "file:../emdash-mika",
    "emdash": "^1.2.0"
  }
}

Published package

Use this mode only after the package is available from the registry and the version supports your EmDash range.

npm install @bnomei/emdash-mika "astro@^7.3.8" "emdash@^1.2.0"

Pin EmDash inside the peer range from ../emdash-mika/package.json when you need repeatable installs.

Release Checklist

Before documenting a public npm install @bnomei/emdash-mika flow as the only path:

• confirm the package exists on npm;
• confirm the published version contains the reviewed 0.2.0 contracts;
• confirm the EmDash peer range matches the EmDash version you recommend;
• replace file:../emdash-mika in template docs or clearly mark it as local development;
• rerun the docs build and inspect dist/llms.txt so agents receive the same status.

Next: Quickstart: Seeded Template runs the source-backed host app. Use Install when wiring a separate Astro + EmDash app.

External References

• EmDash getting started for EmDash’s current Node and project setup guidance.
• npm package spec for file: dependencies and package metadata fields.

Source Anchors

• ⓟ ../emdash-mika/package.json
• ⓟ ../emdash-mika/README.md
• ⓣ ../emdash-mika-template/package.json
• ⓣ ../emdash-mika-template/docs/usage.md