Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
master
6c6d399e feat(vite): add compiler option to vite plugin for tsgo support (#35429) ## Description Adds a `compiler` option to the `@nx/vite` plugin, mirroring the same option already in `@nx/js` (added in #33821). This lets users specify an alternative TypeScript compiler for the inferred `typecheck` target — specifically `tsgo` from `@typescript/native-preview` (TypeScript 7 Go compiler). ## Problem `@nx/vite` hardcodes `'tsc'` for typecheck while `@nx/js` already supports a configurable `compiler` option. Users who want `tsgo` have to patch `@nx/vite` manually. ## Solution 3 lines in `packages/vite/src/plugins/plugin.ts`: 1. Add `compiler?: string` to `VitePluginOptions` (with JSDoc) 2. `options.compiler ?? 'tsc'` instead of hardcoded `'tsc'` (Vue projects still use `vue-tsc`) 3. `options.compiler ??= 'tsc'` in `normalizeOptions` ## Usage ```json // nx.json { "plugins": [ { "plugin": "@nx/vite/plugin", "options": { "compiler": "tsgo" } } ] } ``` ## Benchmarks (large monorepo, ~400 projects) | Project | `tsc` | `tsgo` | Speedup | |---|---|---|---| | `dashboard-web` | 2.33s | 0.43s | **5.4×** | | `market-react` | 11.57s | 3.64s | **3.2×** | On CI: total typecheck CPU dropped **2.7×**, allowing us to eliminate worker sharding entirely. Currently working around this with a pnpm patch on `@nx/vite` — happy to remove it once this lands. ## Prior art - #33821 — same `compiler` option added to `@nx/js` - #35047 / #35167 — Nx team experimented with tsgo internally --------- Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
by Lucas Estevão
Succeeded
master
6c6d399e feat(vite): add compiler option to vite plugin for tsgo support (#35429) ## Description Adds a `compiler` option to the `@nx/vite` plugin, mirroring the same option already in `@nx/js` (added in #33821). This lets users specify an alternative TypeScript compiler for the inferred `typecheck` target — specifically `tsgo` from `@typescript/native-preview` (TypeScript 7 Go compiler). ## Problem `@nx/vite` hardcodes `'tsc'` for typecheck while `@nx/js` already supports a configurable `compiler` option. Users who want `tsgo` have to patch `@nx/vite` manually. ## Solution 3 lines in `packages/vite/src/plugins/plugin.ts`: 1. Add `compiler?: string` to `VitePluginOptions` (with JSDoc) 2. `options.compiler ?? 'tsc'` instead of hardcoded `'tsc'` (Vue projects still use `vue-tsc`) 3. `options.compiler ??= 'tsc'` in `normalizeOptions` ## Usage ```json // nx.json { "plugins": [ { "plugin": "@nx/vite/plugin", "options": { "compiler": "tsgo" } } ] } ``` ## Benchmarks (large monorepo, ~400 projects) | Project | `tsc` | `tsgo` | Speedup | |---|---|---|---| | `dashboard-web` | 2.33s | 0.43s | **5.4×** | | `market-react` | 11.57s | 3.64s | **3.2×** | On CI: total typecheck CPU dropped **2.7×**, allowing us to eliminate worker sharding entirely. Currently working around this with a pnpm patch on `@nx/vite` — happy to remove it once this lands. ## Prior art - #33821 — same `compiler` option added to `@nx/js` - #35047 / #35167 — Nx team experimented with tsgo internally --------- Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
by Lucas Estevão
Failed
35429
Fix ready→
1e8df3fb feat(vite): add compiler option to vite plugin for tsgo support Mirrors the existing compiler option in @nx/js plugin (added in #33821). Allows users to specify an alternative TypeScript compiler (e.g. tsgo from @typescript/native-preview) for the inferred typecheck target. Usage in nx.json: { "plugin": "@nx/vite/plugin", "options": { "compiler": "tsgo" } } Fixes: the @nx/vite plugin hardcodes 'tsc' while @nx/js already supports a configurable compiler. This brings parity between the two plugins.
by Lucas Estevão