Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Exact

Failed
20.3.x
67255189 docs(nx-dev): remove webinar notifier & event link (#29737) Commented out the `WebinarNotifier` in `_app.tsx` and the live event link section in `hero.tsx`. (cherry picked from commit ae9aa5ac76ecaea6f6e6f38a4d67c08a35e5332d)
12 days ago by bcabanes
Succeeded
20.3.x
c97d54b8 docs(core): add local cache information for powerpack (#29630)      ## Current Behavior  ## Expected Behavior  Also includes update ENV variables ## Related Issue(s)  Fixes # (cherry picked from commit cad265dad6d985cdb1aa722409c0c57769bd3e22)
13 days ago by Cammisuli
Failed
20.3.x
b40decc4 docs(core): add local cache information for powerpack (#29630)      ## Current Behavior  ## Expected Behavior  Also includes update ENV variables ## Related Issue(s)  Fixes # (cherry picked from commit cad265dad6d985cdb1aa722409c0c57769bd3e22)
13 days ago by Cammisuli
Failed
20.3.x
9696210a fix(testing): e2e config generators should prompt for missing serve data (#29660) ## Current Behavior When running the `configuration` generator from `@nx/playwright` and `@nx/cypress` for existing appliactions - they currently generate a config that is likely to be invalid becaue there is not enough information to correctly assume the port, target and baseUrl for the application. This data is provided by the application generators that call the `configuration` generator - but that means that users running it manually must remember to pass the information via flags. ## Expected Behavior If the serve data is missing, prompt the user to input the correct information to ensure the config generation is as accurate as possible. (cherry picked from commit bc0566f4c3d7785d05659cb6eccf03531e489995)
19 days ago by Coly010
Succeeded
20.3.x
7bc8269e fix(core): check only for watcher connections during inactivity shutdown (#29621)      ## Current Behavior  We currently second guess our inactivity timer by checking if there are any open connections. However, there's also a strong chance that plugin workers will remain open as long as the daemon is open. This means the daemon stays alive forever and the daemon never shuts down even though it is inactive. ## Expected Behavior  Instead of checking for open connections in general, the daemon server will only check for open file watchers. Most Daemon client requests will restart the server when sending messages so we can safely shut the server down in most cases. The only case where shutting down the daemon would cause a disruption is if a file watcher is registered. In those cases, the daemon will not shutdown due to inactivity. ## Related Issue(s)  Fixes # (cherry picked from commit 32a2ca8eaa016b6868b31b34b32f2a5091589ede)
20 days ago by FrozenPandaz
Failed
20.3.x
7bc8269e fix(core): check only for watcher connections during inactivity shutdown (#29621)      ## Current Behavior  We currently second guess our inactivity timer by checking if there are any open connections. However, there's also a strong chance that plugin workers will remain open as long as the daemon is open. This means the daemon stays alive forever and the daemon never shuts down even though it is inactive. ## Expected Behavior  Instead of checking for open connections in general, the daemon server will only check for open file watchers. Most Daemon client requests will restart the server when sending messages so we can safely shut the server down in most cases. The only case where shutting down the daemon would cause a disruption is if a file watcher is registered. In those cases, the daemon will not shutdown due to inactivity. ## Related Issue(s)  Fixes # (cherry picked from commit 32a2ca8eaa016b6868b31b34b32f2a5091589ede)
21 days ago by FrozenPandaz
Succeeded
20.3.x
fae2455f docs(misc): nx 20.3 blogpost (#29512)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # (cherry picked from commit 3f3c8747c6b48ac4f9915289d415fd12096d4fe6)
29 days ago by ZackDeRose
Succeeded
20.3.x
5c51d92f fix(js): infer outputs correctly when both rootDir and outDir are set for tsconfig (#29531) When the tsconfig has `rootDir` and `outDir` both defined, then the `*.tsbuildinfo` file is not cached. This makes incremental tsc not work through distribution (e.g. agents). For example, given this `tsconfig.lib.json` file: ```json { "compilerOptions": { "outDir": "out-tsc/lib-1", "rootDir": "src" } } ``` The outputs (e.g. `*.d.ts` files) are under `{projectRoot}/out-tsc/lib-1`, but the tsbuild info file is under `{projectRoot}/out-tsc/tsconfig.lib.tsbuildinfo`. ## Current Behavior tsbuildinfo file is not cached ## Expected Behavior tsbuildinfo file is cached ## Related Issue(s)  Fixes # --------- Co-authored-by: Leosvel Pérez Espinosa <leosvel.perez.espinosa@gmail.com> (cherry picked from commit df27a97c7e9c18fe3b39a70bbff071c11c02b724)
29 days ago by jaysoo