---

Building

# Vite dev server for the browser with HMR.
bazel run //packages/dashql-app:dev

# For Electron renderer HMR, run these in separate terminals.
bazel run //packages/dashql-app:dev -- --mode electron
bazel run //packages/dashql-native:dev
# Override DASHQL_ELECTRON_RENDERER_URL if Vite uses another loopback HTTP origin.

# If you need demangled wasm stacktraces, run with
bazel run --config=debug //packages/dashql-app:dev

# We bundle the web app with two routers
# - '/'-paths for Cloudflare Pages -> :pages
# - '#/'-paths for native apps -> :reloc
bazel build //packages/dashql-app:pages
bazel build //packages/dashql-app:reloc

# Astro dev server for the website and blog (dashql.org) on http://localhost:9003.
# It runs from the node_modules of the workspace, run `pnpm install` once first.
bazel run //packages/dashql-org:dev
# Static build of the website for Cloudflare Pages
bazel build //packages/dashql-org:pages_deploy

# The native app can be cross-compiled for arm and x86
bazel run //packages/dashql-native:mac_package_arm64
bazel run //packages/dashql-native:mac_package_x86_64

# Test everything
bazel test //...

# Many tests are backed by snapshots / fixtures
# /snapshots/*.tpl.yaml are the input to generate /snapshots/*.yaml
# Update a snapshot category after intentional changes:
bazel run //snapshots/analyzer:update
bazel run //snapshots/completion:update
bazel run //snapshots/diff:update
bazel run //snapshots/formatter:update
bazel run //snapshots/parser:update
bazel run //snapshots/planner:update
bazel run //snapshots/plans/hyper/tests:update
bazel run //snapshots/visualize:update

# Upgrade the Rust crates declared in bazel/crates/*.MODULE.bazel
bazel run //scripts:repin_crates -- full

# Generate rust-project.json for rust-analyzer in IDEs (see docs/agents/rust_analyzer.md)
bazel run //scripts:rust_project

# Fetch test datasets
bazel build //packages/dashql-datasets:datasets
# Upload missing test datasets to data.dashql.app (requires R2 key)
bazel run //packages/dashql-datasets:sync

---

Continuous Deployment

• We're continuously deploying main to dashql.app
  • //packages/dashql-app:pages is published to Cloudflare Pages
  • We use aggressive caching with cache busting
• Native apps and update bundles are published to get.dashql.app
• We're maintaining release manifests under get.dashql.app/stable.json and get.dashql.app/canary.json
• Hosted test datasets are published to data.dashql.app (R2 bucket dashql-data)
  • Built hermetically by //packages/dashql-datasets (hash-pinned sources -> DuckDB CLI) and mirrored with bazel run //packages/dashql-datasets:sync
  • Immutable versioned paths data.dashql.app/<dataset>/v<version>/<file>.parquet, plus a mutable data.dashql.app/index.json registry
• Our builds heavily rely on a bazel-remote cache server under bazel-cache.dashql.app
• You can see bazel cache statistics here