Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36605
f83d1a8a fix(vitest): do not rewrite dirname in key or import positions ## Current Behavior The migration rewrote `__dirname` anywhere it appeared as an identifier, including positions where `import.meta.dirname` is not legal syntax: - `const { __dirname: dir } = opts` - `import { __dirname as dir } from './paths.mjs'` - `export { __dirname } from './paths.mjs'` Each produced an unparseable config. ## Expected Behavior Rename keys, aliased import specifiers, and re-exports are left alone. Real references in the same file are still rewritten. ## Related Issue(s) NXC-4772
by Jack Hsu
Failed
36605
Flaky task→
f83d1a8a fix(vitest): do not rewrite dirname in key or import positions ## Current Behavior The migration rewrote `__dirname` anywhere it appeared as an identifier, including positions where `import.meta.dirname` is not legal syntax: - `const { __dirname: dir } = opts` - `import { __dirname as dir } from './paths.mjs'` - `export { __dirname } from './paths.mjs'` Each produced an unparseable config. ## Expected Behavior Rename keys, aliased import specifiers, and re-exports are left alone. Real references in the same file are still rewritten. ## Related Issue(s) NXC-4772
by Jack Hsu
Succeeded
36605
7c6a8048 fix(vitest): use esm config files and import.meta.dirname ## Current Behavior Vite 8.2 warns that Nx-generated configs use features `configLoader: 'native'` cannot support: - `__dirname` in `vitest.config.mts` - ESM syntax in a CommonJS-loaded root `vitest.config.ts` `@nx/vite` fixed this in 22.1.1. `@nx/vitest` forked before that and kept `__dirname`. ## Expected Behavior No warning. - `__dirname` -> `import.meta.dirname` (3 sites, matching `@nx/vite`) - root aggregator written as `vitest.config.mts` - vitest 3 `vitest.workspace.ts` -> `.mts` - nuxt emits `.mts` unless the workspace is on eslintrc, where legacy `@nuxt/eslint-config` cannot parse it - migration backfills `__dirname` in existing `.mts`/`.mjs` configs ## Related Issue(s) NXC-4772
by Jack Hsu
Failed
36605
Flaky task→
7c6a8048 fix(vitest): use esm config files and import.meta.dirname ## Current Behavior Vite 8.2 warns that Nx-generated configs use features `configLoader: 'native'` cannot support: - `__dirname` in `vitest.config.mts` - ESM syntax in a CommonJS-loaded root `vitest.config.ts` `@nx/vite` fixed this in 22.1.1. `@nx/vitest` forked before that and kept `__dirname`. ## Expected Behavior No warning. - `__dirname` -> `import.meta.dirname` (3 sites, matching `@nx/vite`) - root aggregator written as `vitest.config.mts` - vitest 3 `vitest.workspace.ts` -> `.mts` - nuxt emits `.mts` unless the workspace is on eslintrc, where legacy `@nuxt/eslint-config` cannot parse it - migration backfills `__dirname` in existing `.mts`/`.mjs` configs ## Related Issue(s) NXC-4772
by Jack Hsu
Canceled
36605
7c6a8048 fix(vitest): use esm config files and import.meta.dirname ## Current Behavior Vite 8.2 warns that Nx-generated configs use features `configLoader: 'native'` cannot support: - `__dirname` in `vitest.config.mts` - ESM syntax in a CommonJS-loaded root `vitest.config.ts` `@nx/vite` fixed this in 22.1.1. `@nx/vitest` forked before that and kept `__dirname`. ## Expected Behavior No warning. - `__dirname` -> `import.meta.dirname` (3 sites, matching `@nx/vite`) - root aggregator written as `vitest.config.mts` - vitest 3 `vitest.workspace.ts` -> `.mts` - nuxt emits `.mts` unless the workspace is on eslintrc, where legacy `@nuxt/eslint-config` cannot parse it - migration backfills `__dirname` in existing `.mts`/`.mjs` configs ## Related Issue(s) NXC-4772
by Jack Hsu