You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our Nx workspace is comprised of Angular micro-frontend projects and when developing on our local machines, we have no issues with the Nx CLI. However, when we trigger our Azure DevOps CI/CD pipeline, the Nx CLI commands are recognized but the Nx projects in the workspace are not detected. For example, running nx show projects returns nothing and project names are not found when including them in targets like nx test project-name. We are also in the correct working directory running commands at the root of the workspace and did try the latest version of Nx. No errors occur when installing Nx, however we do receive this warning
Our pipeline's native target does differ as the native target is wasm32 while our local machines use x86_64-windows. However, before escalating changing the target to our DevOps department, we are wondering if anyone has encountered similar issues with wasm32. Were there any necessary configuration steps needed, a specific Nx version that was reliable, or any additional dependencies needed? We do not use any WebAssembly in our project. We did see in the Nx docs that msvc is explicitly supported and want to verify that changing the target is a preferred approach. Otherwise, we would greatly appreciate any help troubleshooting.
Expected Behavior
After installing dependencies (including Nx) via yarn install, we expect commands incorporating project names in the workspace to be recognized and executed.
yarn install --immutable
YN0000: · Yarn 4.4.0
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 0s 671ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0066: │ typescript@patch:typescript@npm%3A5.7.2#optional!builtin<compat/typescript>::version=5.7.2&hash=74658d: Cannot apply hunk #1
➤ YN0013: │ 1867 packages were added to the project (+ 1.07 GiB).
➤ YN0000: └ Completed in 53s 858ms
➤ YN0000: ┌ Link step
➤ YN0007: │ esbuild@npm:0.24.0 must be built because it never has been before or the last one failed
➤ YN0007: │ @swc/core@npm:1.9.3 [742cb] must be built because it never has been before or the last one failed
➤ YN0007: │ nx@npm:19.5.7 [6de38] must be built because it never has been before or the last one failed
➤ YN0007: │ esbuild@npm:0.21.5 must be built because it never has been before or the last one failed
➤ YN0007: │ @parcel/watcher@npm:2.5.0 must be built because it never has been before or the last one failed
➤ YN0007: │ msgpackr-extract@npm:3.0.3 must be built because it never has been before or the last one failed
➤ YN0007: │ lmdb@npm:3.0.12 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 8m 59s
➤ YN0000: · Done with warnings in 9m 54s
nx test WebApp1
NX Cannot find project 'WebApp1'
Current Behavior
Our Nx workspace is comprised of Angular micro-frontend projects and when developing on our local machines, we have no issues with the Nx CLI. However, when we trigger our Azure DevOps CI/CD pipeline, the Nx CLI commands are recognized but the Nx projects in the workspace are not detected. For example, running nx show projects returns nothing and project names are not found when including them in targets like nx test project-name. We are also in the correct working directory running commands at the root of the workspace and did try the latest version of Nx. No errors occur when installing Nx, however we do receive this warning
Our pipeline's native target does differ as the native target is wasm32 while our local machines use x86_64-windows. However, before escalating changing the target to our DevOps department, we are wondering if anyone has encountered similar issues with wasm32. Were there any necessary configuration steps needed, a specific Nx version that was reliable, or any additional dependencies needed? We do not use any WebAssembly in our project. We did see in the Nx docs that msvc is explicitly supported and want to verify that changing the target is a preferred approach. Otherwise, we would greatly appreciate any help troubleshooting.
Expected Behavior
After installing dependencies (including Nx) via yarn install, we expect commands incorporating project names in the workspace to be recognized and executed.
GitHub Repo
No response
Steps to Reproduce
yarn install --immutable
// name of the project is WebApp1
nx test WebApp1
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
{
"name": "ccl-web",
"version": "0.0.0",
"license": "MIT",
"private": true,
"dependencies": {
"@angular/animations": "18.1.4",
"@angular/common": "18.1.4",
"@angular/compiler": "18.1.4",
"@angular/core": "18.1.4",
"@angular/forms": "18.1.4",
"@angular/platform-browser": "18.1.4",
"@angular/platform-browser-dynamic": "18.1.4",
"@angular/platform-server": "18.1.4",
"@angular/router": "18.1.4",
"@angular/ssr": "18.1.4",
"@ionic/angular": "8.2.6",
"@ionic/angular-server": "8.2.6",
"@ionic/angular-toolkit": "11.0.1",
"@maskito/angular": "3.0.0",
"@maskito/core": "3.0.0",
"@maskito/kit": "3.0.0",
"@ngrx/signals": "18.0.2",
"@nx/angular": "19.5.7",
"aws-amplify": "6.5.0",
"aws-cdk": "2.151.0",
"aws-cdk-templates": "1.0.202-2.8",
"caniuse-lite": "1.0.30001651",
"express": "4.19.2",
"libphonenumber-js": "1.11.5",
"rxjs": "7.8.1",
"tslib": "2.3.0",
"uniqolor": "1.1.1",
"vest": "5.4.1",
"zone.js": "0.14.3"
},
"devDependencies": {
"@angular-builders/jest": "18.0.0",
"@angular-devkit/architect": "^0.1801.4",
"@angular-devkit/build-angular": "18.1.4",
"@angular-devkit/core": "18.1.4",
"@angular-devkit/schematics": "18.1.4",
"@angular-eslint/eslint-plugin": "18.2.0",
"@angular-eslint/eslint-plugin-template": "18.2.0",
"@angular-eslint/template-parser": "18.2.0",
"@angular/cli": "18.1.4",
"@angular/compiler-cli": "18.1.4",
"@angular/language-service": "18.1.4",
"@nx/devkit": "19.5.7",
"@nx/eslint": "19.5.7",
"@nx/eslint-plugin": "19.5.7",
"@nx/jest": "19.5.7",
"@nx/js": "19.5.7",
"@nx/playwright": "19.5.7",
"@nx/storybook": "19.5.7",
"@nx/web": "19.5.7",
"@nx/workspace": "19.5.7",
"@playwright/test": "1.46.0",
"@schematics/angular": "18.1.4",
"@storybook/addon-a11y": "8.2.8",
"@storybook/addon-essentials": "8.2.8",
"@storybook/addon-interactions": "8.2.8",
"@storybook/addon-links": "8.2.8",
"@storybook/angular": "8.2.8",
"@storybook/core-common": "8.2.8",
"@storybook/core-server": "8.2.8",
"@storybook/jest": "0.2.3",
"@storybook/preset-scss": "1.0.3",
"@storybook/test-runner": "0.19.1",
"@storybook/testing-library": "0.2.2",
"@swc-node/register": "1.10.9",
"@swc/core": "1.9.3",
"@swc/helpers": "0.5.15",
"@swc/types": "^0.1.17",
"@swc/wasm": "1.9.3",
"@types/express": "4.17.21",
"@types/jest": "29.5.12",
"@types/node": "18.16.9",
"@types/typescript": "^2.0.0",
"@typescript-eslint/eslint-plugin": "7.18.0",
"@typescript-eslint/parser": "7.18.0",
"@typescript-eslint/utils": "8.0.1",
"css-loader": "^7.1.2",
"eslint": "8.57.0",
"eslint-config-prettier": "9.1.0",
"eslint-plugin-playwright": "1.6.2",
"eslint-plugin-storybook": "0.8.0",
"jest": "29.7.0",
"jest-environment-jsdom": "29.7.0",
"jest-preset-angular": "14.2.2",
"nx": "19.5.7",
"prettier": "3.3.3",
"sass-loader": "16.0.0",
"storybook": "8.2.8",
"style-loader": "4.0.0",
"ts-jest": "29.1.0",
"ts-node": "10.9.1",
"typescript": "5.5.2",
"webpack": "^5.93.0"
},
"packageManager": "[email protected]"
}
The text was updated successfully, but these errors were encountered: