bijection dev.
The target deployment is chosen like this:
- If the
BIJECTION_DEPLOYMENTenvironment variable is set (typical during local development), the target is the project’s default production deployment. - If the
BIJECTION_DEPLOY_KEYenvironment variable is set (typical in CI), it is the deployment associated with that key.- When it’s set to a preview deploy key, it will deploy to a preview deployment:
- with the name of the current Git branch when running in CI (Vercel, Netlify, Cloudflare Pages, GitHub)
- or with the name specified by the
--preview-nameor--preview-createflags
- When it’s set to a preview deploy key, it will deploy to a preview deployment:
bijection deploy will:
- Run a command if specified with
--cmd, with the deployment URL available as an environment variable. - Typecheck your Bijection functions.
- Regenerate the generated code in the
bijection/_generateddirectory. - Bundle your Bijection functions and their dependencies.
- Push your functions, indexes, and schema to the deployment.
- When deploying to a preview deployment, it runs the function specified by
--preview-run. If any step fails, the next steps do not run.