Updating Mira

Updates are free for buyers. When a new version is released, download it again from the link in your purchase email or from your Lemon Squeezy orders.

Before you update

Commit your project to Git, or copy the whole folder somewhere safe.

If you changed content and settings only

Your own work lives in a few places:

• src/site.config.ts
• src/content/ (pages, conditions, treatments, clinics, team, posts)
• src/assets/images/ (your photos), and any illustrations you added to src/assets/art/
• public/ (favicon and any files you added)
• src/i18n/languages.mjs, and any words you changed in src/i18n/ui.ts
• site and any font changes in astro.config.mjs
• colour changes in scripts/palette.mjs (run npm run palette again after updating)
• wrangler.jsonc, if you deploy to Cloudflare Workers

1. Unzip the new version into a new folder.
2. Copy those files and folders from your project into it, replacing the samples.
3. Run npm install, then npm run dev, and check everything looks right.
4. Read the release notes. If a block gained a new setting or a word was added to ui.ts, npm run check tells you which file needs it.

If you changed the design

Compare your changed files with the new version and copy your changes across. In VS Code, select two files in the explorer, right-click and choose Compare Selected.

Updating Astro

Mira is tested with the Astro version in its package.json. To try a newer one:

npx @astrojs/upgrade

Then run npm run check and npm run build. If anything breaks, go back to your saved version and wait for the next Mira release.