Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
master
5ccc0a8c fix(misc): use string type for fetchDepth in azure-pipelines.yml (#33727) The Azure Pipelines schema requires fetchDepth to be a string, but the generator was outputting a number. This fix changes the value to a string to match the official schema specification. ## Current Behavior The generator creates `azure-pipelines.yml` with `fetchDepth: 0` (number), which causes YAML schema validation error because the Azure Pipelines schema expects `fetchDepth` to be a string. According to the [Azure Pipelines schema](https://raw.githubusercontent.com/microsoft/azure-pipelines-vscode/master/service-schema.json), `fetchDepth` is defined as: ```json "fetchDepth": { "description": "Depth of Git graph to fetch", "$ref": "#/definitions/string" } ``` ## Expected Behavior The generator should output `fetchDepth: '0'` (string) to match the schema specification and prevent validation errors. Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
5 hours ago by fALKENdk
Succeeded
33727
cd7b6760 Merge branch 'master' into fix/azure-pipelines-yaml-schema
6 hours ago by fALKENdk
Failed
33727
cd7b6760 Merge branch 'master' into fix/azure-pipelines-yaml-schema
9 hours ago by fALKENdk
Succeeded
33727
4b6c9f31 Merge branch 'master' into fix/azure-pipelines-yaml-schema
1 day ago by fALKENdk
Failed
33727
f53bda7e Merge branch 'master' into fix/azure-pipelines-yaml-schema
5 days ago by fALKENdk
Succeeded
master
cb5510d2 fix(storybook): conditionally include node imports only for non-angular frameworks (#33728) ## Current Behavior The fileURLToPath and dirname imports are only used in the getAbsolutePath function, which is only generated for non-Angular Storybook projects. ## Expected Behavior This change prevents unnecessary imports from being added to Angular Storybook configurations.
6 days ago by fALKENdk
Succeeded
master
cb5510d2 fix(storybook): conditionally include node imports only for non-angular frameworks (#33728) ## Current Behavior The fileURLToPath and dirname imports are only used in the getAbsolutePath function, which is only generated for non-Angular Storybook projects. ## Expected Behavior This change prevents unnecessary imports from being added to Angular Storybook configurations.
7 days ago by fALKENdk
Succeeded
master
cb5510d2 fix(storybook): conditionally include node imports only for non-angular frameworks (#33728) ## Current Behavior The fileURLToPath and dirname imports are only used in the getAbsolutePath function, which is only generated for non-Angular Storybook projects. ## Expected Behavior This change prevents unnecessary imports from being added to Angular Storybook configurations.
7 days ago by fALKENdk
Failed
master
cb5510d2 fix(storybook): conditionally include node imports only for non-angular frameworks (#33728) ## Current Behavior The fileURLToPath and dirname imports are only used in the getAbsolutePath function, which is only generated for non-Angular Storybook projects. ## Expected Behavior This change prevents unnecessary imports from being added to Angular Storybook configurations.
7 days ago by fALKENdk
Failed
master
cb5510d2 fix(storybook): conditionally include node imports only for non-angular frameworks (#33728) ## Current Behavior The fileURLToPath and dirname imports are only used in the getAbsolutePath function, which is only generated for non-Angular Storybook projects. ## Expected Behavior This change prevents unnecessary imports from being added to Angular Storybook configurations.
7 days ago by fALKENdk
Failed
master
cb5510d2 fix(storybook): conditionally include node imports only for non-angular frameworks (#33728) ## Current Behavior The fileURLToPath and dirname imports are only used in the getAbsolutePath function, which is only generated for non-Angular Storybook projects. ## Expected Behavior This change prevents unnecessary imports from being added to Angular Storybook configurations.
7 days ago by fALKENdk
Failed
master
cb5510d2 fix(storybook): conditionally include node imports only for non-angular frameworks (#33728) ## Current Behavior The fileURLToPath and dirname imports are only used in the getAbsolutePath function, which is only generated for non-Angular Storybook projects. ## Expected Behavior This change prevents unnecessary imports from being added to Angular Storybook configurations.
7 days ago by fALKENdk
Succeeded
33728
42214dea Merge branch 'master' into fix/storybook-conditional-imports
7 days ago by fALKENdk
Succeeded
33727
4e3f7b9b Merge branch 'master' into fix/azure-pipelines-yaml-schema
8 days ago by fALKENdk
Succeeded
33727
78230950 fix(misc): use string type for fetchDepth in azure-pipelines.yml The Azure Pipelines schema requires fetchDepth to be a string, but the generator was outputting a number. This fix changes the value to a string to match the official schema specification.
8 days ago by fALKENdk
Canceled
master
3c5e40be fix(nest): set moduleResolution to node to prevent TS5095 error (#33607) When generating NestJS applications in Angular workspaces, the base tsconfig sets moduleResolution to 'bundler' which causes TS5095 errors because 'bundler' requires module to be 'preserve' or 'es2015+'. NestJS applications should use Node.js module resolution instead. This fix sets moduleResolution to 'node' for NestJS applications (except when using TS solution setup, which uses 'nodenext'). Fixes #33589
21 days ago by fALKENdk
Succeeded
33607
d5ae87c3 fix(nest): set moduleResolution to node to prevent TS5095 error When generating NestJS applications in Angular workspaces, the base tsconfig sets moduleResolution to 'bundler', which causes TS5095 errors because 'bundler' requires module to be 'preserve' or 'es2015+'. NestJS applications should use Node.js module resolution instead. This fix sets moduleResolution to 'node' for NestJS applications (except when using TS solution setup, which uses 'nodenext'). closed #33589
21 days ago by fALKENdk