Optional Deno step
Deno is not required and does nothing unless configured. It exists so a Deno build or asset step can run before the main application build, and it is configured through the environment rather than inputs — which means a job can enable it without the action’s signature changing.
Precedence: environment > inputs > defaults. With nothing set, Deno is skipped.
| Variable | Meaning |
|---|---|
DENO_ENABLE |
true/1/yes/on — enable even without a build command. |
DENO_BUILD |
The command to run, e.g. deno task build. |
DENO_VERSION |
e.g. v1.44.x. |
DENO_WORKDIR |
Working directory. Defaults to .. |
Pass-throughs when present: DENO_AUTH_TOKEN, DENO_DIR, HTTP_PROXY,
HTTPS_PROXY, NO_PROXY.
Job-level
Section titled “Job-level”jobs: build: runs-on: ubuntu-latest env: DENO_VERSION: 'v1.44.x' DENO_WORKDIR: 'frontend' DENO_BUILD: 'deno task build' steps: - uses: actions/checkout@v7 - uses: dAppCore/build@v4 with: build-name: myAppFrom a previous step
Section titled “From a previous step”- run: | echo "DENO_ENABLE=true" >> "$GITHUB_ENV" echo "DENO_BUILD=deno task build" >> "$GITHUB_ENV"- uses: dAppCore/build@v4 with: build-name: myAppPrivate modules
Section titled “Private modules”env: DENO_AUTH_TOKEN: ${{ secrets.DENO_AUTH_TOKEN }}