Clarify site build and deploy scripts

This commit is contained in:
2026-08-13 19:53:38 +09:00
parent 62aa81b91c
commit 8198b615a8
3 changed files with 13 additions and 9 deletions
+5 -3
View File
@@ -83,8 +83,10 @@ npm run build
```
`npm run build:wasm` builds both generated WebAssembly packages.
`npm run build:runtime` writes generated runtime files into `packages/decodal-wasm/`.
`npm run build:tools` writes generated language tools files into `packages/decodal-codemirror/wasm/`.
`npm run build:wasm:runtime` writes generated runtime files into `packages/decodal-wasm/`.
`npm run build:wasm:formatter` writes generated formatter files into `packages/decodal-codemirror/wasm/`.
`npm run build` builds only the static site from the current package files.
Use `npm run build:all` to regenerate both WebAssembly packages and then build the static site in one command.
These generated files are committed so the site can be built without requiring every consumer to regenerate the wasm packages first.
@@ -158,7 +160,7 @@ CLOUDFLARE_PROJECT_NAME=my-pages-project npm run deploy
If the committed WASM package must be regenerated before deploy, use:
```sh
npm run deploy:wasm
npm run deploy:all
```
## Tree-sitter grammar