Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Failed
master
c7e2782e docs(nx-dev): render keywords meta tag (#29450) Renders `keywords` property from frontmatter as a `<meta>` tag.
7 hours ago by leosvelperez
Failed
master
c7e2782e docs(nx-dev): render keywords meta tag (#29450) Renders `keywords` property from frontmatter as a `<meta>` tag.
7 hours ago by FrozenPandaz
Succeeded
master
c7e2782e docs(nx-dev): render keywords meta tag (#29450) Renders `keywords` property from frontmatter as a `<meta>` tag.
9 hours ago by JamesHenry
Succeeded
master
c7e2782e docs(nx-dev): render keywords meta tag (#29450) Renders `keywords` property from frontmatter as a `<meta>` tag.
12 hours ago by isaacplmann
Failed
master
d7ffba8f fix(core): daemon spinner should show text (#29448)      ## Current Behavior Daemon spinner doesn't show up ## Expected Behavior Daemon spinner shows properly ## Related Issue(s)  Fixes #
17 hours ago by AgentEnder
Succeeded
master
81c66eca fix(js): not generate tsconfig if already exists (#29317)      ## Current Behavior  - in serve target, it uses executor `@nx/webpack:dev-server` - in `packages/webpack/src/executors/dev-server/dev-server.impl.ts`, when buildLibsFromSource is false, it calls createTmpTsConfig to create a temp config - in webpack.config.js, it has `module.exports = composePlugins(withNx()`. in withNx, it calls NxTsconfigPathsWebpackPlugin. - when buildLibsFromSource is false, it called createTmpTsConfig again based on the temp config. it created an infinite loop because it creates a tsconfig that extends itself. ## Expected Behavior  - do not create a temp config if it is a generated ts config ## Related Issue(s)  Fixes https://github.com/nrwl/nx/issues/28006
18 hours ago by xiongemi
Failed
master
7498e470 feat(nx-dev): link more customer videos on enterprise page
20 hours ago by juristr
Failed
master
6e41b30f docs(nx): Version error in documentation page (#29440) Original text was: e.g. `nx@19.2.0` and `@nx/js@20.2.0` should be used together. Surely it should be... e.g. `nx@19.2.0` and `@nx/js@19.2.0` should be used together.
20 hours ago by jimmcslim
Failed
master
85166343 fix(nuxt): change tsconfig path on server part (#28864) ## Current Behavior On a new workspace with nuxt preset (`npx create-nx-workspace@latest --preset=nuxt`), a `tsconfig.json` file is create on the nuxt server side directory (path: `apps/nuxt-test/src/server/tsconfig.json`). The file extends the building nuxt server tsconfig file (path: `apps/nuxt-test/.nuxt/tsconfig.server.json`) with the following value : ```json { "extends": "../.nuxt/tsconfig.server.json" } ``` ## Expected Behavior This `tconfig.json` file generate need to extends the `tsconfig.server.json` with the good path Fixes # The correct value is ```json { "extends": "../../.nuxt/tsconfig.server.json" } ```
21 hours ago by yvalentin
Failed
master
ba37a2f9 chore(repo): bump nx to 20.3.0-rc.0 (#29437) Bumps Nx
22 hours ago by AgentEnder
Failed
master
3a164a22 feat(nx-plugin): added support for vitest test runner (#29140)      ## Current Behavior  Nx Plugin do not have the option to use Vitest as test runner ## Expected Behavior  This PR allow us to use Vitest as test runner in plugins projects. Vitest for e2e targets is still missing and a new PR will be raised after https://github.com/nrwl/nx/issues/29139 is fixed ## Related Issue(s)  Fixes #22882
22 hours ago by gperdomor
Succeeded
master
2143ea5e fix(angular): set up host and remote ssr apps correctly #29442 (#29447) ## Current Behavior During the update to support Angular 19, the host and remote generators' `updateSsrSetup` function was missed. This led to the creation of a second `server.ts` file, which would result in the node server trying to instantiate twice. ## Expected Behavior Fix the path normalization dependent on angular major version to ensure only one server will be instantiated. ## Related Issue(s) Fixes #29442
22 hours ago by Coly010
Failed
master
efa5ba2b fix(core): update yarn-parser to handle yarn v4 syntax (#29067) Update the yarn-parser so that yarn.lock file generation works with yarn v4 ## Current Behavior yarn.lock is not correctly created when using yarn v4 ``` "": version: 1.22.8 resolution: "resolve@patch:resolve@npm%3A1.22.8#optional!builtin<compat/resolve>::version=1.22.8&hash=c3c19d" dependencies: is-core-module: "npm:^2.13.0" path-parse: "npm:^1.0.7" supports-preserve-symlinks-flag: "npm:^1.0.0" bin: resolve: bin/resolve checksum: 0446f024439cd2e50c6c8fa8ba77eaa8370b4180f401a96abf3d1ebc770ac51c1955e12764cde449fde3fff480a61f84388e3505ecdbab778f4bef5f8212c729 languageName: node linkType: hard ``` ## Expected Behavior yarn.lock should be created correctly with no missing keys ## Related Issue(s)  Fixes #19881
1 day ago by leosvelperez
Failed
master
efa5ba2b fix(core): update yarn-parser to handle yarn v4 syntax (#29067) Update the yarn-parser so that yarn.lock file generation works with yarn v4 ## Current Behavior yarn.lock is not correctly created when using yarn v4 ``` "": version: 1.22.8 resolution: "resolve@patch:resolve@npm%3A1.22.8#optional!builtin<compat/resolve>::version=1.22.8&hash=c3c19d" dependencies: is-core-module: "npm:^2.13.0" path-parse: "npm:^1.0.7" supports-preserve-symlinks-flag: "npm:^1.0.0" bin: resolve: bin/resolve checksum: 0446f024439cd2e50c6c8fa8ba77eaa8370b4180f401a96abf3d1ebc770ac51c1955e12764cde449fde3fff480a61f84388e3505ecdbab778f4bef5f8212c729 languageName: node linkType: hard ``` ## Expected Behavior yarn.lock should be created correctly with no missing keys ## Related Issue(s)  Fixes #19881
1 day ago by FrozenPandaz
Succeeded
master
efa5ba2b fix(core): update yarn-parser to handle yarn v4 syntax (#29067) Update the yarn-parser so that yarn.lock file generation works with yarn v4 ## Current Behavior yarn.lock is not correctly created when using yarn v4 ``` "": version: 1.22.8 resolution: "resolve@patch:resolve@npm%3A1.22.8#optional!builtin<compat/resolve>::version=1.22.8&hash=c3c19d" dependencies: is-core-module: "npm:^2.13.0" path-parse: "npm:^1.0.7" supports-preserve-symlinks-flag: "npm:^1.0.0" bin: resolve: bin/resolve checksum: 0446f024439cd2e50c6c8fa8ba77eaa8370b4180f401a96abf3d1ebc770ac51c1955e12764cde449fde3fff480a61f84388e3505ecdbab778f4bef5f8212c729 languageName: node linkType: hard ``` ## Expected Behavior yarn.lock should be created correctly with no missing keys ## Related Issue(s)  Fixes #19881
1 day ago by a88zach
Succeeded
master
09800062 fix(core): graph spinners should update properly (#29433) ## Current Behavior Spinners are not updated properly ## Expected Behavior Spinners are updated properly ## Related Issue(s)  Fixes #
1 day ago by JamesHenry
Succeeded
master
09800062 fix(core): graph spinners should update properly (#29433) ## Current Behavior Spinners are not updated properly ## Expected Behavior Spinners are updated properly ## Related Issue(s)  Fixes #
2 days ago by AgentEnder
Failed
master
16c8ba16 fix(module-federation): dynamic federation helpers should normalize remote names (#29427) ## Current Behavior After migration of existing remotes beyond Nx 19.8, dynamic manifest federation files may be updated to match the normalized names of JS variables (`_` instead of `-`). Project names will not have been migrated, and therefore the logic to find the projects based on the remote names is broken. ## Expected Behavior Check the project graph for remote names as-is and by transforming `_` to `-` to see if the project exists
2 days ago by Coly010
Failed
master
3c3d2e5f feat(core): show progress on ci if graph construction takes longer than expected (#29392) Progress spinners currently only show up when the terminal is a tty. This updates it to show static text on CI, but at a longer duration
2 days ago by AgentEnder
Succeeded
master
ba1641d7 fix(bundling): ensure vitest timestamp files are ignored (#29418) ## Current Behavior Vitest TS config files produce timestamp temp files during project graph creation which are cleaned up. However, the creation and deletion of these files triggers the daemon to recalculate graph. It ends up in a loop. The vite timestamp files were already added to the gitignore to prevent this. ## Expected Behavior Add vitest timestamp files to gitignore
2 days ago by Coly010