Run development and quality checks with Bun #290

New Issue

2026-10-17T02:35:37+02:00

nessar commented

2026-10-17 02:35:37 +02:00

What to build

A developer can install dependencies, start and watch the
Angular application, build it for production, and run native lint, formatting,
and standalone type checks using the verified Bun release. The corresponding CI
validation and build jobs exercise the same behavior.

Acceptance criteria

Pin the verified Bun release in the development setup and affected CI
validation/build jobs. Frozen installs succeed from a clean checkout and
leave the lockfile unchanged.
Language-registry generation, development serving, watch mode, and
production builds execute project-owned JavaScript and child tools under
Bun with Node unavailable to those commands. Preserve Angular's standard
compiler, bundler, and development-server behavior.
Replace ESLint with the verified native Bun lint setup in one cohesive
change, updating all affected callers and configuration. Preserve rule
severities, deprecated API detection, unused-name exceptions, and failure
exit codes; remove superseded dependencies only after checking their uses.
Replace Prettier with the verified native formatter for existing
application, repository-script, and workflow checks. Preserve configured
formatting and Angular-template handling without an unrelated reformat.
Use Bun's native standalone checker for application and test TypeScript,
including test files as the test runner changes in ticket 03. Keep
TypeScript 6 for Angular compilation and template checking.
Reuse the probes established by ticket 01 to show that representative lint,
formatting, application/test type, and template violations fail. Successful
standalone checking must not substitute for the Angular production build.
Update the affected CI jobs and development command documentation together,
including the native commands and the TypeScript coexistence boundary.
Work on the shared Bun integration branch. Keep test-runner replacement in
ticket 03 and HTTP/container serving in ticket 04; completion of the whole
migration remains gated by ticket 05, with no temporary dual quality tools.

Blocked by

#289 — Verify Bun and Angular compatibility

## What to build A developer can install dependencies, start and watch the Angular application, build it for production, and run native lint, formatting, and standalone type checks using the verified Bun release. The corresponding CI validation and build jobs exercise the same behavior. ## Acceptance criteria - [ ] Pin the verified Bun release in the development setup and affected CI validation/build jobs. Frozen installs succeed from a clean checkout and leave the lockfile unchanged. - [ ] Language-registry generation, development serving, watch mode, and production builds execute project-owned JavaScript and child tools under Bun with Node unavailable to those commands. Preserve Angular's standard compiler, bundler, and development-server behavior. - [ ] Replace ESLint with the verified native Bun lint setup in one cohesive change, updating all affected callers and configuration. Preserve rule severities, deprecated API detection, unused-name exceptions, and failure exit codes; remove superseded dependencies only after checking their uses. - [ ] Replace Prettier with the verified native formatter for existing application, repository-script, and workflow checks. Preserve configured formatting and Angular-template handling without an unrelated reformat. - [ ] Use Bun's native standalone checker for application and test TypeScript, including test files as the test runner changes in ticket 03. Keep TypeScript 6 for Angular compilation and template checking. - [ ] Reuse the probes established by ticket 01 to show that representative lint, formatting, application/test type, and template violations fail. Successful standalone checking must not substitute for the Angular production build. - [ ] Update the affected CI jobs and development command documentation together, including the native commands and the TypeScript coexistence boundary. - [ ] Work on the shared Bun integration branch. Keep test-runner replacement in ticket 03 and HTTP/container serving in ticket 04; completion of the whole migration remains gated by ticket 05, with no temporary dual quality tools. ## Blocked by - #289 — Verify Bun and Angular compatibility

nessar added the ready-for-agent label 2026-10-17 02:35:37 +02:00

nessar referenced this issue

2026-10-17 02:35:38 +02:00

Complete and verify the Bun CI cutover #293

nessar added a new dependency 2026-10-17 02:35:38 +02:00

#289 Verify Bun and Angular compatibility

nessar added a new dependency 2026-10-17 02:35:38 +02:00

#293 Complete and verify the Bun CI cutover

nessar referenced this issue from a commit

2026-10-17 16:10:35 +02:00

ci: run development, quality checks and CI on Bun 1.4.3

nessar referenced this issue