Configuration
How to personalize Vaxla to your workspace.
By default, Vaxla could cover most cases without any configuration. However, if you wish to customize, we should provide full type-safety.
Folder Location
We select the configuration file based on the following priority:
- Any directory flag in a CLI command like
--dir
. Not recommended long-term. - In the
package.json
file, like:{ "vaxla": { "config": "example/vaxla" } }
. - The
vaxla
ortools/vaxla
folder if it exists. - We build the configuration file by scanning the file system for
package.json
files.
It's recommended to place your Vaxla configuration inside of vaxla
or tools/vaxla
. If you have a convention, please share it with us!
Vaxla can be dropped into any project, here is an example of how you may setup your Vaxla configuration:
Personalizing
Packages
Packages tend to represent a single application or service (usually with an associated package.json
file). Packages can be organized in any way and don't need to have a folder.
The color
of the package is a variable originating from tailwindcss's color palette.
Scripts
Scripts run code that controls your workspace, the same way you would run a command in your terminal. Traditionally, scripts are defined in the package.json
file, Vaxla allows you to define scripts in a more flexible way.
Common scripts: dev
, build
, preview
, test
, seed
, deploy
.
Commands can either be a shell command, or a function. All scripts run in an isolated child process. There are plenty of ways to define shell scripts (though they all resolve to a string).
External Links
Specify external links to save and share links directing to other internal documentation.
Users often link their Figma, internal wikis, and cloud tooling.