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?

The core package source currently identifies @bnomei/emdash-mika as version 0.0.0. The sibling seeded template depends on it with 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. This workspace proves the local package and template relationship; a public host app should use the registry path only after a non-0.0.0 Mika package is published and its peer ranges match the host.

Source-Of-Truth Ranges

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

Surface	Current source value
Package name	@bnomei/emdash-mika
Package version	0.0.0
Node engine	>=22.12.0
Astro peer	`^6.0.0
EmDash peer	>=0.22.0 <1.0.0
Stripe peer	>=16.0.0 <21.0.0
Published file set	dist and src/templates
Copyable template export	./templates/astro/*

The seeded GitHub template raises the local Node engine to >=22.13.0, uses Astro ^7.0.0, and depends on Mika through file:../emdash-mika.

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": ">=0.22.0 <1.0.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 "emdash@>=0.22.0 <1.0.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 is not 0.0.0;
• 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