Overview - Nx-oss-repo

Nx-OSS-Repo

7 Days

30 Days

Latest CI Pipeline Executions (CIPEs)

Exact

Succeeded
master
c2af06e0 docs(angular) : add cd instruction to move inside workspace directory (#28135) `npx nx serve angular-store` this would not work if the user does not move to the directory first.      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # Co-authored-by: Isaac Mann <isaacplmann@users.noreply.github.com>
49 minutes ago by mann-codes...
Failed
master
9efde91a fix(core): plugins should not be registered twice and should respect shutdown queue (#22057)
8 hours ago by pull
Failed
master
e864d35b fix(core): ensure migrate works with yarn PnP (#21824)
8 hours ago by pull
Succeeded
master
75c1da32 chore(repo): update to 20.0.0-beta.8 (#28300)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: Jonathan Cammisuli <jon@cammisuli.ca>
10 hours ago by JamesHenry
Succeeded
master
75c1da32 chore(repo): update to 20.0.0-beta.8 (#28300)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: Jonathan Cammisuli <jon@cammisuli.ca>
15 hours ago by jaysoo
Succeeded
master
cbda8cf2 fix(testing): getJestProjectsAsync no longer duplicates project paths (#28311)      ## Current Behavior Using `getJestProjectsAsync` to include both `project.json` and inferred targets can result in errors due to duplcicated paths. You see an error like this: ``` Error: Whoops! Two projects resolved to the same config path: /Users/jack/projects/ocean/libs/nx-cloud/data-access-organization-dashboard/jest.config.ts: Project 1: /Users/jack/projects/ocean/libs/nx-cloud/data-access-organization-dashboard/jest.config.ts Project 2: /Users/jack/projects/ocean/libs/nx-cloud/data-access-organization-dashboard This usually means that your "projects" config includes a directory that doesn't have any configuration recognizable by Jest. Please fix it. at ensureNoDuplicateConfigs (/Users/jack/projects/ocean/node_modules/jest-config/build/index.js:325:13) at readConfigs (/Users/jack/projects/ocean/node_modules/jest-config/build/index.js:474:5) at processTicksAndRejections (node:internal/process/task_queues:95:5) at async runCLI (/Users/jack/projects/ocean/node_modules/jest-cli/node_modules/@jest/core/build/cli/index.js:151:59) at async Object.run (/Users/jack/projects/ocean/node_modules/jest-cli/build/run.js:130:37) ``` ## Expected Behavior Using `getJestProjectsAsync` should work and include all inferred projects. ## Related Issue(s)  Fixes #
16 hours ago by jaysoo
Succeeded
master
d7140995 fix(core): handle unique constraint errors when adding duplicate hashes to the cache db (#28310)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
18 hours ago by Cammisuli
Succeeded
master
acb19a64 fix(nx-cloud): use create-workspace-v1 endpoint if v2 returns with 404 (#28015)      ## Current Behavior  By default we connect all workspaces to Nx Cloud via the V2 connect endpoint. ## Expected Behavior  Certain users (on-prem or single tenant) may not have access to the V2 endpoint, and so we should fall back to V1 so as not to prevent new workspaces from being created. ## Related Issue(s)  Fixes #
19 hours ago by lourw
Failed
master
f743808b fix(testing): migration for getJestProjects -> getJestProjectsAsync handles both CJS and ESM (#28299) This PR updates the Jest migration so it handles both CJS and ESM format for Jest config file. We now generate with ESM so those need to be handled. There are four combinations: 1. `require` (CJS) with `module.export` (CJS) 2. `import` (ESM) with `export default` (ESM) 3. `require` (CJS) with `export default` (ESM) 4. `import` (ESM) with `module.export` (CJS) (1) and (2) should cover almost all cases, and (3) and (4) are there just in case. If the format isn't matching what we generate, then just bail.      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
22 hours ago by jaysoo
Succeeded
master
27beba81 docs(core): release blog post (#28275)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: Isaac Mann <isaacplmann@users.noreply.github.com> Co-authored-by: Jack Hsu <jack.hsu@gmail.com>
23 hours ago by mhartington
Succeeded
master
63e0f278 fix(react): host generator should pass normalized name to remote generator (#28295)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
24 hours ago by Coly010
Succeeded
master
c6bb33a4 docs(nx-dev): rename images with invalid Windows filenames
1 day ago by philipjful...
Failed
master
9efde91a fix(core): plugins should not be registered twice and should respect shutdown queue (#22057)
1 day ago by pull
Failed
master
e864d35b fix(core): ensure migrate works with yarn PnP (#21824)
1 day ago by pull
Succeeded
master
7c0e3440 fix(release): ensure updateDependents only works for independent projects (#28283)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
1 day ago by JamesHenry
Succeeded
master
7c0e3440 fix(release): ensure updateDependents only works for independent projects (#28283)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
1 day ago by fahslaj
Succeeded
master
d5c45219 feat(core): enable db cache by default (#28048)      ## Current Behavior DB cache is disabled by default ## Expected Behavior DB cache is enabled by default ## Related Issue(s)  Fixes #
1 day ago by Cammisuli
Succeeded
master
d477ea7b docs(core): ts project references guide (#28281) Adds a TS project references guide
2 days ago by isaacplmann
Failed
master
23bebd91 feat(devkit): bump compatibility to Nx 19 - 21.x (#28243) BREAKING CHANGE      ## Current Behavior  * `@nx/devkit` supports Nx 17 - 20. * Node 18 - 22 is supported * `ExecutorContext.projectGraph`, `ExecutorContext.nxJsonConfiguration`, and `ExecutorContext.projectsConfigurations` is marked as optional because `ExecutorContext` in some versions of Nx did not have them. * `ExecutorContext.workspace` is marked as optional because `ExecutorContext` in some versions of Nx did not have the above properties which contain the same information. * `ProjectGraphNode` is deprecated. * `NxPluginV1.processProjectGraph` was deprecated long ago and there has been a warning since. * `appRootPath` has been deprecated for a long time. * `parseTargetString` had a variant that did not take either the project graph or the executor context. * `readNxJson` has a variant which does not take a tree. This was not clearly deprecated. * There are handlers to require from `@nx/` instead of `@nrwl` * Nx tries to get a root install from `@nrwl/cli` ## Expected Behavior  * `@nx/devkit` supports Nx 19 - 21. * Node 20 - 22 is supported * `ExecutorContext.projectGraph`, `ExecutorContext.nxJsonConfiguration`, and `ExecutorContext.projectsConfigurations` is marked as required because `ExecutorContext` in Nx 19+ is guaranteed to have them. * `ExecutorContext.workspace` is removed because the same information is available in the above properties * `ProjectGraphNode` is removed. * `NxPluginV1` is no more. All plugins should be `NxPluginV2`. * `workspaceRoot` is the replacement for `appRootPath`. `appRootPath` is removed. * `parseTargetString` no longer has a variant that did not take either the project graph or the executor context. * `readNxJson` still has a variant which does not take a tree but it's clearly deprecated to be removed in Nx 21. * `@nrwl` packages are no more so we don't have to redirect requires anymore. * `@nrwl/cli` is no more so Nx shouldn't try to get a root install there * ## Related Issue(s)  Fixes #
2 days ago by FrozenPandaz
Succeeded
master
d131b0b6 docs(core): nx 20 changelog (#28270) - Add a changelog for Nx 20.0.0 - Demo the composite graph view in `Explore Your Workspace`
2 days ago by isaacplmann