Multiple npm-scripts in craft-cloud.yaml

[jamesmacwhite]

Currently you can specify a single script name to run during the deployment process.

It would be great to be able to run multiple commands during a deployment e.g. unit tests or other scripts alongside a typical build.

[timkelty]

Would be nice indeed…

That said, it is pretty easy to just use NPM's native pre/post hooks and/or &&:

"prebuild": "npm run types && npm run test",
"build": "vite build",
"test": "vitest",
"types": "tsc --noEmit",

[jamesmacwhite]

Ah! I wasn't sure if you can chain the npm-script value as it's stated in the documentation for the craft-cloud.yaml that it should be a simple name with no bash, which technically && would be logic and not plain text.

[AugustMiller]

Ah, yeah—that's mostly true. The npm-script key in cloud.yaml must match the name of a script in your package.json, but the script itself can contain whatever sh-supported operators you want!

[jamesmacwhite]

Good to know. Maybe a small addition to the docs to clarify? To me it reads as only a single script name is allowed.

npm-script — A single script name. Arbitrary Bash (including other npx commands) is not allowed. (Default: build)

[timkelty]

Yeah, I agree it reads awkwardly. I think perhaps the reference to "Arbitrary Bash (including other npx commands) is not allowed" confuses the issue.

@AugustMiller will know better, but it could read like:

A key from the NPM "scripts" object to run at build-time. (Default: build)