- I don't think I've ever used the "require" block feature of the build.json
- Writing the command out as a comma separated list of arguments is tedious.
Backwards-compatible improvement:
build.ini
[script/**/*.es6]
require=node *,babel *,webpack *
execute=./node_modules/.bin/esbuild script/script.es6 --bundle --sourcemap --outfile=www/script.js --loader:.es6=js --target=chrome105,firefox105,edge105,safari15
[style/**/*.scss]
require=sass 1.6.*
execute=sass ./style/style.scss ./www/style.css
Then we can continue the default behaviour of build.ini, build.production.ini.
Then there's a new issue for WebEngine to determine what the environment is by which config file is present (config.production.ini = production = load build.production.ini).
Backwards-compatible improvement:
build.ini
Then we can continue the default behaviour of
build.ini,build.production.ini.Then there's a new issue for WebEngine to determine what the environment is by which config file is present (config.production.ini = production = load build.production.ini).