wptom update

npx wptom update --dry-run   # see what would change
npx wptom update

Run it inside your site’s folder. It downloads the template’s latest released version and merges it into your project. Your changes stay. New to this? Follow Keep your site up to date step by step.

Usage

wptom update [--dry-run]

Option	Meaning
`--dry-run`	Show what would change and stop. Nothing is written.

Up to date already? aurora is up to date (1.0.0). and nothing else happens.

How it decides, file by file

It compares three versions of every file: the one you started from (.wptom/base/), yours now, and the new release.

Situation	What happens	Shown as
You didn’t touch the file	It takes the new version	`~ path`
Only you changed it	Yours stays	(not listed)
You both changed it, different lines	Merged line by line	`⇄ path merged with your edits`
You both changed the same lines	Conflict markers for you to resolve	`! path conflict: resolve the <<<<<<< markers`
A binary file (photo, font) changed on both sides	Yours stays; the new one is saved as `path.wptom-new`	`? path.wptom-new new version saved next to yours`
New file in the release	Added	`+ path`
New file, but you already have a different one there	Yours stays; theirs saved as `.wptom-new`	`? path.wptom-new`
Removed in the release, you never changed it	Deleted	`- path`
Removed in the release, but you changed it	Kept	`= path kept (removed upstream but edited)`
You deleted it	Stays deleted	`= path kept (deleted by you)`

The summary line counts them: 3 updated · 1 conflicts · 0 removed. With conflicts or .wptom-new files, it asks Some files need your attention afterwards. Apply the update? first; answer No and nothing changes (Update cancelled. Nothing changed.).

After updating, .wptom/base/ and .wptom/meta.json move to the new version, and it ends with Updated to aurora@1.1.0. If there were conflicts: Resolve the conflict markers, then run your build. git diff shows everything that changed.

Conflicts

A conflict looks like this in the file:

<<<<<<< yours: src/content/singletons/site.json
  "tagline": "Ship faster with Northlight",
=======
  "tagline": "Find the signal in your product data.",
>>>>>>> wptom update

Keep what you want, delete the three marker lines, save. Step by step with VS Code.

Good to know

Commit first. Then git diff shows exactly what the update changed and git restore . undoes it.
Git must be installed: merging uses git merge-file. Without Git, every file changed on both sides becomes a conflict with your version and the new one one after the other.
Run npm install afterwards: a new version can bump packages (including the @wptom/* integrations).
Variants stay: a site created with --cms emdash is updated with the EmDash variant of the new version. If a release dropped that variant: aurora@2.0.0 no longer offers the "emdash" option. Nothing changed.
Your project name in package.json is kept.
PRO templates need an active license on this computer (wptom login).

Errors

Message	Fix
`No .wptom/meta.json here. Run wptom update inside a site created with wptom new.`	`cd` into your site’s folder. Sites not made with `wptom new` can’t be updated this way.
`.wptom/base is missing, so your edits can't be told apart from upstream.`	Restore `.wptom/base/` (e.g. from a backup), or create a fresh site and move your content over.
`aurora has no published version.`	The template has no release yet.

More: Errors and fixes.