Update Phaser in project templates
Run the checked-in script in phaser-editor-v5-starter-templates, not in the Editor monorepo. Never hardcode /Users/arian/.... Never commit .env.
This skill does not upload. After it, use skill upload-templates.
It also does not copy Phaser into the Scene Editor (skill update-scene-editor-phaser).
Do this
- Find the templates repo (folder that contains
update-phaser.js,build.js, andeditor-starter-template-vite/). Typical location: sibling ofphaser-editor-v5($PHASEREDITOR5_HOME/phaser-editor-v5-starter-templates). PHASER_PATHmust be the parent of aphaser/clone. If unset, the script uses a siblingphaser/next to the templates repo. The clone’spackage.jsonversionis what gets installed.- Check:
./update-phaser-all.sh --check
- Update every template and bump marketplace
template.jsonintegers:
./update-phaser-all.sh
--skip-increment if you only wanted the Phaser pin and will bump versions yourself.
- Report the Phaser version that was applied. Remind the user:
- skill
upload-templates/./publish-templates.shto build + CDN - then
phaser-editor-v5/desktop/get-starter-templates.sh(vite / webpack / basic-javascript are not on the CDN)
- skill
The build host is usually an Apple Silicon Mac; this skill only needs Node and npm (any Mac is fine).
Invariants
- Node templates:
npm install phaser@<version>(package.json+phasereditor2d.config.json). - Plain JS (basic-javascript):
index.htmljsDelivrphaser.min.js+ copytypes/phaser.d.tsandmatter.d.ts. phaser-site/(New Project “Phaser” list) is not touched.- Built-ins have no
template.json; increment only affects marketplace folders. - Needs
types/phaser.d.tsin the Phaser clone (npm run tsgenthere if missing).
Never
- Run
upload-release/s3://phaser/downloads/editor/for these zips. - Commit
build/or.env. - Invent a Phaser version; read it from
$PHASER_PATH/phaser/package.json.
More detail
- Guide:
phaser-editor-v5/developer-docs/templates.md - Upload: skill
upload-templates