Tags: nrwl/nx
Tags
feat(core): allow circular project dependencies to execute tasks (#28227 ) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> If there are project dependencies and not all projects contain the same task target, a circular dependency error is shown. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> If not all circular dependent projects contain the same task target, allow execution of the target. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
fix(testing): getJestProjectsAsync no longer duplicates project paths (… …#28311) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## 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) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
docs(nx-dev): rename images with invalid Windows filenames
fix(nx-cloud): use create-workspace-v1 endpoint if v2 returns with 404 ( #28015) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> By default we connect all workspaces to Nx Cloud via the V2 connect endpoint. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> 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) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes # (cherry picked from commit acb19a6)
chore(core): expose utility to determine if db cache is enabled (#28262) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> There is no function to determine if the db cache is enabled ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> There is a function to determine if the db cache is enabled. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
fix(core): change getCache signature to only accept options (#28248) <!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> `getCache` has an argument for nxjson. This breaks nx cloud when using the db cache. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> `getCache` now only has options as an argument, and uses `readNxJson` in the function body ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
feat(misc): remove @nrwl/ scoped packages (#27858) This PR removes the `@nrwl/*` packages. Also cleans up references to the legacy packages. NOTE: The rescope page is now under `/deprecated/rescope`. There is still >1000K monthly traffic to it, which might be due to older Nx users. <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
PreviousNext