eslint workflow (viser-project/viser)

The eslint workflow from viser-project/viser, explained and optimized by Latchkey.

What it does

This is the eslint workflow from the viser-project/viser repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: eslint

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

concurrency:
  group: eslint-${{ github.ref }}
  cancel-in-progress: true

jobs:
  eslint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Use Node.js
        uses: actions/setup-node@v6
        with:
          node-version: 24
          cache: npm
          cache-dependency-path: src/viser/client/package-lock.json
      - name: Run eslint
        # Use npm (the repo's lockfile is package-lock.json, not yarn.lock) so
        # installs are deterministic and cacheable, matching the other client
        # workflows.
        run: |
          cd src/viser/client
          npm ci
          npx eslint .

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: eslint
 
on:
  push:
    branches: [main]
  pull_request:
    branches: [main]
 
concurrency:
  group: eslint-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  eslint:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
      - name: Use Node.js
        uses: actions/setup-node@v6
        with:
          node-version: 24
          cache: npm
          cache-dependency-path: src/viser/client/package-lock.json
      - name: Run eslint
        # Use npm (the repo's lockfile is package-lock.json, not yarn.lock) so
        # installs are deterministic and cacheable, matching the other client
        # workflows.
        run: |
          cd src/viser/client
          npm ci
          npx eslint .
 

What changed

• Run on Latchkey managed runners with one line (runs-on), which apply the fixes below automatically and self-heal transient failures. This example uses latchkey-small; pick the runner size that fits the job.
• Add a job timeout so a hung step cannot burn hours of runner time.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Dependency installs

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow