Q: The plugin isn't loading. What's wrong?

Confirm dashcommerce() is inside EmDash's plugins array in astro.config — not parallel to emdash() . Typos in the config silently fail surprisingly often. Compare against the Getting started snippet verbatim.

Q: Does DashCommerce have a separate migrate CLI?

No. EmDash applies core database migrations as part of bun emdash seed (and when running emdash init or emdash dev in typical setups). DashCommerce does not require a second migration CLI — wire the plugin, run npx dashcommerce-merge-seed , then bun emdash seed , then start the app so plugin lifecycle hooks can run.

Q: Seeding fails with schema errors — what do I check?

Re-run npx dashcommerce-merge-seed against the current @dashcommerce/core version. This merges DashCommerce's required product collection and taxonomies into your seed file, deduped by slug/name. If you hand-edited the JSON, verify defineProductsCollection() sits under top-level collections and taxonomies under taxonomies . Confirm emdash seed and dashcommerce-merge-seed target the same file — package.json → emdash.seed or .emdash/seed.json .

Question 1

The plugin isn't loading. What's wrong?

Accepted Answer

Confirm dashcommerce() is inside EmDash's plugins array in astro.config — not parallel to emdash(). Typos in the config silently fail surprisingly often. Compare against the Getting started snippet verbatim.

Question 2

Does DashCommerce have a separate migrate CLI?

Accepted Answer

No. EmDash applies core database migrations as part of bun emdash seed (and when running emdash init or emdash dev in typical setups). DashCommerce does not require a second migration CLI — wire the plugin, run npx dashcommerce-merge-seed, then bun emdash seed, then start the app so plugin lifecycle hooks can run.

Question 3

Seeding fails with schema errors — what do I check?

Accepted Answer

Re-run npx dashcommerce-merge-seed against the current @dashcommerce/core version. This merges DashCommerce's required product collection and taxonomies into your seed file, deduped by slug/name. If you hand-edited the JSON, verify defineProductsCollection() sits under top-level collections and taxonomies under taxonomies. Confirm emdash seed and dashcommerce-merge-seed target the same file — package.json → emdash.seed or .emdash/seed.json.

Question 4

Stripe checkout fails with key errors — what's wrong?

Accepted Answer

Check three things: (1) secret vs publishable keys — secret keys start with sk_, publishable with pk_; (2) test vs live mode — test keys contain test; (3) where keys are saved — DashCommerce reads from the EmDash admin's DashCommerce settings, not from a local .env alone. Watch server logs when submitting a PaymentIntent; Stripe's API errors are explicit once you see the response body.

Question 5

Webhooks aren't firing in production — what do I check?

Accepted Answer

Confirm the webhook endpoint URL in your Stripe dashboard points to your deployed URL (not localhost). Verify the signing secret matches what DashCommerce is expecting — version-specific; check CHANGELOG. Check server logs for signature verification failures. For local testing, use stripe listen --forward-to localhost:4321/api/stripe/webhook.

Question 6

Where can I get more help?

Accepted Answer

Open a focused issue on GitHub with your EmDash version, DashCommerce version, a minimal config snippet (redact secrets), and the exact error string. For EmDash CMS questions, see the EmDash repo.

Troubleshooting

Plugin not loading

emdash migrate does not exist

Seed errors

Checkout or admin errors after Stripe

This marketing site’s waitlist API

Still stuck?