Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Failed
main
a6934c12 chore(repo): disable pnpm install cache `resolve-required-data` job (#32791) Fix publish pipeline by running `pnpm install` when using `setup-node`. (cherry picked from commit 4d57e62ce823e341e5480fcda0f320052607d11a)
by Jack Hsu
J
Succeeded
master
f9abfb69 docs(misc): adjust margins and reorder intro for "Add to existing project" (#36598) While going through the getting started pages, I noticed a few issues. 1. Youtube player does not have margins around it, so spacing is too tight with intro paragraphs. <img width="822" height="645" alt="image" src="https://github.com/user-attachments/assets/fa22d40c-f5b9-4da2-a050-868066e254ab" /> 2. `Start with an existing project` page should have prompt first, then intro sentence/paragraph, then video, like we do on other pages. <img width="840" height="888" alt="image" src="https://github.com/user-attachments/assets/988399dc-e6a4-4368-a4f5-e11a6d767a11" /> --- Fixed 1: <img width="774" height="656" alt="Screenshot 2026-08-07 at 9 01 58 AM" src="https://github.com/user-attachments/assets/00adac1e-f8bf-4ec2-882a-f39951836096" /> Fixed 2: <img width="843" height="1059" alt="Screenshot 2026-08-07 at 9 02 08 AM" src="https://github.com/user-attachments/assets/5ff8d6af-5237-4e7c-b6a6-41390ff07a6a" /> --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: jaysoo <jaysoo@users.noreply.github.com>
by Jack Hsu
Succeeded
master
f9abfb69 docs(misc): adjust margins and reorder intro for "Add to existing project" (#36598) While going through the getting started pages, I noticed a few issues. 1. Youtube player does not have margins around it, so spacing is too tight with intro paragraphs. <img width="822" height="645" alt="image" src="https://github.com/user-attachments/assets/fa22d40c-f5b9-4da2-a050-868066e254ab" /> 2. `Start with an existing project` page should have prompt first, then intro sentence/paragraph, then video, like we do on other pages. <img width="840" height="888" alt="image" src="https://github.com/user-attachments/assets/988399dc-e6a4-4368-a4f5-e11a6d767a11" /> --- Fixed 1: <img width="774" height="656" alt="Screenshot 2026-08-07 at 9 01 58 AM" src="https://github.com/user-attachments/assets/00adac1e-f8bf-4ec2-882a-f39951836096" /> Fixed 2: <img width="843" height="1059" alt="Screenshot 2026-08-07 at 9 02 08 AM" src="https://github.com/user-attachments/assets/5ff8d6af-5237-4e7c-b6a6-41390ff07a6a" /> --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: jaysoo <jaysoo@users.noreply.github.com>
by Jack Hsu
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
Succeeded
master
13072779 docs(misc): clean up intro and getting-started onboarding pages (#36595) ## Current Behavior Intro page mentions a couple of deepdives on how to run tasks and if you can use Nx in single repo (not monorepo). Both aren't important on this page -> remove. "Start a New Project" offers two paths: `create-nx-workspace` and Nx Cloud browser onboarding. Templates read as four starters. Neither onboarding page has an AI prompt or sample timings. Intro carries two deep-dive callouts. ## Expected Behavior Tightens intro page, removes Nx Console since it's covered in `Editor setup` page. "Start a New Project" is CNW only. The template section says the four short names are shortcuts and points at the gallery. Both onboarding pages get a copyable agent prompt and an example run block, borrowed from the Nx Cloud get-started page. Intro deep-dive callouts folded into one line each. Both init and CNW pages now have `CI setup` and `AI setup` as next steps since those are important now (no more `Editor setup`). Previews: - https://deploy-preview-36595--nx-docs.netlify.app/docs/getting-started/intro - https://deploy-preview-36595--nx-docs.netlify.app/docs/getting-started/start-new-project - https://deploy-preview-36595--nx-docs.netlify.app/docs/getting-started/start-with-existing-project ## Related Issue(s) DOC-579  --- <p><picture><source media="(prefers-color-scheme: dark)" srcset="https://static.ops.cloud.nx.app/polygraph/session-logo-v4-dark.svg"><img src="https://static.ops.cloud.nx.app/polygraph/session-logo-v4-light.svg" width="16" height="22" align="middle" alt="Polygraph"></picture> <a href="https://snapshot.app.trypolygraph.com/orgs/69cdc268b6aa527e4129c2b4/sessions/noble-osprey-dd3ebfa3">View session ↗</a></p> 
by Jack Hsu
Succeeded
master
13072779 docs(misc): clean up intro and getting-started onboarding pages (#36595) ## Current Behavior Intro page mentions a couple of deepdives on how to run tasks and if you can use Nx in single repo (not monorepo). Both aren't important on this page -> remove. "Start a New Project" offers two paths: `create-nx-workspace` and Nx Cloud browser onboarding. Templates read as four starters. Neither onboarding page has an AI prompt or sample timings. Intro carries two deep-dive callouts. ## Expected Behavior Tightens intro page, removes Nx Console since it's covered in `Editor setup` page. "Start a New Project" is CNW only. The template section says the four short names are shortcuts and points at the gallery. Both onboarding pages get a copyable agent prompt and an example run block, borrowed from the Nx Cloud get-started page. Intro deep-dive callouts folded into one line each. Both init and CNW pages now have `CI setup` and `AI setup` as next steps since those are important now (no more `Editor setup`). Previews: - https://deploy-preview-36595--nx-docs.netlify.app/docs/getting-started/intro - https://deploy-preview-36595--nx-docs.netlify.app/docs/getting-started/start-new-project - https://deploy-preview-36595--nx-docs.netlify.app/docs/getting-started/start-with-existing-project ## Related Issue(s) DOC-579  --- <p><picture><source media="(prefers-color-scheme: dark)" srcset="https://static.ops.cloud.nx.app/polygraph/session-logo-v4-dark.svg"><img src="https://static.ops.cloud.nx.app/polygraph/session-logo-v4-light.svg" width="16" height="22" align="middle" alt="Polygraph"></picture> <a href="https://snapshot.app.trypolygraph.com/orgs/69cdc268b6aa527e4129c2b4/sessions/noble-osprey-dd3ebfa3">View session ↗</a></p> 
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
Succeeded
36601
fc6f6b30 docs(misc): apply review feedback to add-language-support walkthrough ## Current Behavior Walkthrough lacks agent prompt and plugin skeleton, says proof/worked-example/this-guide phrasing, tools/ path, and claims migrations ship for internal APIs. ## Expected Behavior Adds project.json aside + llm copy prompt + entry-point skeleton, packages/nx-uv path, plugin name matches package.json note, inputs reference link, lockfile tradeoff, nx show project mention, internal utils framed as promoted-later, next steps replaced with performant-plugin pointer. ## Related Issue(s) DOC-569
by Jack Hsu
Succeeded
36601
fc6f6b30 docs(misc): apply review feedback to add-language-support walkthrough ## Current Behavior Walkthrough lacks agent prompt and plugin skeleton, says proof/worked-example/this-guide phrasing, tools/ path, and claims migrations ship for internal APIs. ## Expected Behavior Adds project.json aside + llm copy prompt + entry-point skeleton, packages/nx-uv path, plugin name matches package.json note, inputs reference link, lockfile tradeoff, nx show project mention, internal utils framed as promoted-later, next steps replaced with performant-plugin pointer. ## Related Issue(s) DOC-569
by Jack Hsu
Canceled
36601
fc6f6b30 docs(misc): apply review feedback to add-language-support walkthrough ## Current Behavior Walkthrough lacks agent prompt and plugin skeleton, says proof/worked-example/this-guide phrasing, tools/ path, and claims migrations ship for internal APIs. ## Expected Behavior Adds project.json aside + llm copy prompt + entry-point skeleton, packages/nx-uv path, plugin name matches package.json note, inputs reference link, lockfile tradeoff, nx show project mention, internal utils framed as promoted-later, next steps replaced with performant-plugin pointer. ## Related Issue(s) DOC-569
by Jack Hsu