Workspace scripts can be executed with
melos run or will be executed as hooks before/after some
specific Melos commands.
With the simple syntax, only the name of the script and the command to execute needs to be specified:
scripts: hello: echo 'Hello World'
The extends syntax allows for a more complex configuration of a script:
scripts: hello: name: hey description: 'Greet the world' run: echo '$GREETING World' env: GREETING: 'Hey'
A unique identifier for the script.
A short description, shown when using
melos run with no argument.
The command to execute.
A map of environment variables that will be passed to the executed command.
melos exec command allows you to execute a command for multiple packages. When used
in a script, you can declare filter options in the
hello_flutter script below is only executed in Flutter packages:
scripts: hello_flutter: run: melos exec -- "echo 'Hello $(dirname $PWD)'" select-package: flutter: true
See the global options for a list of supported filters.
Certain Melos commands support running scripts before and after the command is executed.
Before hooks have the same name as the command. Post hooks have the name of the command prefixed with
scripts: bootstrap: echo `bootstrap command is running...` postbootstrap: echo `bootstrap command is done`
Currently, the following Melos commands support hooks: