build.md

build

these docs are for production builds, for development see dev.md

usage

The gro build task produces outputs for production:

gro build

This runs the configured Gro plugins, setup -> adapt -> teardown, in production mode.

If your project has a SvelteKit frontend, the default plugin calls vite build, forwarding any -- vite [...] args:

gro build -- vite --config my-config.js

plugins

Plugins are objects that customize the behavior of gro build and gro dev. They try to defer to underlying tools as much as possible, and exist to glue everything together. For example, the library plugin internally uses svelte-package. See plugin.md to learn more.

deploying and publishing

Now that we can produce builds, how do we share them with the world?

The gro deploy task outputs builds to a branch, like for static publishing to GitHub pages.

The gro publish task publishes packages to npm.

Both of these tasks call gro build internally, and you can always run it manually if you're curious.