Tags: iominh/nx
Tags
feat(rspack): respect deleteOutputPath option in rspack executor (nrw… …l#32609) - Add deleteOutputPath option to rspack executor schema - Modify rspack executor to only clean output directory when deleteOutputPath is not explicitly set to false - This aligns rspack executor behavior with webpack executor and allows users to control output cleaning - Fixes issue where rspack.output.clean configuration was being bypassed Fixes nrwl#32015 <!-- 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 --> ## 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 # --------- Co-authored-by: Colum Ferry <[email protected]>
feat(rspack): respect deleteOutputPath option in rspack executor (nrw… …l#32609) - Add deleteOutputPath option to rspack executor schema - Modify rspack executor to only clean output directory when deleteOutputPath is not explicitly set to false - This aligns rspack executor behavior with webpack executor and allows users to control output cleaning - Fixes issue where rspack.output.clean configuration was being bypassed Fixes nrwl#32015 <!-- 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 --> ## 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 # --------- Co-authored-by: Colum Ferry <[email protected]>
feat(misc): add Cookiebot global scripts to astro-docs (nrwl#32660) Adds cookie consent management and analytics tracking to the astro-docs project: - Cookiebot consent script integration with COOKIEBOT_ID environment variable - GlobalScripts React component reused from nx-dev for consistency - Head.astro component override to integrate scripts into Starlight - Cookie consent categories: statistics (GA, GTM) and marketing (HubSpot, Apollo, Hotjar, Twitter) - Production-only script loading with COOKIEBOT_DISABLE bypass option Fixes DOC-95 Co-authored-by: Claude <[email protected]>
chore(repo): update core team in readme (nrwl#32585) <!-- 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 --> ## 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 #
chore(gradle): migrate plugin to 0.1.7 (nrwl#32638) <!-- 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 --> ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Migrate gradle project graph plugin to 0.1.7 ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
fix(nx-cloud): forward --help to nx-cloud aliases (nrwl#32627) <!-- 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 --> `--help` behaviour is defined in the Nx alias entrypoints, and doesn't show the correct output: ``` npx nx start-ci-run --help nx start-ci-run [options] Starts a new CI run for distributed task execution. This command is an alias for [`nx-cloud start-ci-run`](/ci/reference/nx-cloud-cli#npx-nxcloud-start-ci-run). Options: --help Show help [boolean] --version Show version number [boolean] --verbose Prints additional information about the commands (e.g., stack traces). ``` ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> When running `npx nx start-ci-run --help` the help from the file in the NxCloud repo should be displayed: ``` npx nx start-ci-run --help Usage: npx nx-cloud start-ci-run [options] Starts an Nx Cloud CI Pipeline Execution and configures distribution. Options: --distribute-on <config> Configure how to distribute with Nx Agents. Accepts: - "<count> <launchTemplate>" (e.g., "8 linux-medium-js") - path to a .yaml/.yml file for dynamic changesets - "manual" to disable the warning for legacy DTE setups --stop-agents-after <targets> Comma-separated targets that signal agents can stop. Include configuration when needed, e.g., "build:locale-en". --require-explicit-completion Require explicitly completing the CI run with "npx nx-cloud complete-ci-run". --stop-agents-on-failure Stop all agents when a command fails (default: true). --with-env-vars <CSV> Extra env vars to forward to agents in addition to NX_* (e.g., "VAR1,VAR2"). --use-dte-by-default Use this to disable auto-distribution of Nx tasks (default: true) --no-distribution Disable distribution for this run --assignment-rules <file> YAML file with assignment rules (for manual DTE only, see docs) --fix-tasks <csv> Task names to auto fix --force Force start a CIPE even when a CI environment is not detected. --help, -h Show this help and exit. Notes: - Do not run this command locally. If run accidentally, clean up with "npx nx-cloud cleanup". - For legacy manual DTE setups, you can pass "--distribute-on=manual". Examples: npx nx-cloud start-ci-run --distribute-on="8 linux-medium-js" --stop-agents-after=lint,test,build npx nx-cloud start-ci-run --distribute-on=".nx/workflows/dynamic-changesets.yaml" --stop-agents-after=e2e npx nx-cloud start-ci-run --distribute-on="manual" --stop-agents-after=e2e npx nx affected -t lint,test,build Docs: https://nx.dev/ci/reference/nx-cloud-cli#npx-nxcloud-startcirun https://nx.dev/ci/reference/assignment-rules ``` ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #CLOUD-3580
fix(js): store stale references correctly in `typescript-sync` genera… …tor (nrwl#32596) ## Current Behavior The `@nx/js:typescript-sync` wrongly identifies stale project references. ## Expected Behavior The `@nx/js:typescript-sync` should correctly identify stale project references.
fix(rspack): expand serve-static target names for init generator (nrw… …l#32587) ## Current Behavior If another plugin, or project/package.json exists in the repo that has a `serve-static` target, running `nx add @nx/rpsack` will fail. The `@nx/rspack:init` generator does not have any alternative names for `serve-static` causing conflicts. ## Expected Behavior The `init` generator should provide more options for the `serve-static` target such that the plugin can be added without error.
docs(misc): fix issues with base href, rewrites, and connecting next.… …js and astro docs (nrwl#32484) This PR fixes issues with connecting new Astro docs with the `/docs` rewrite rule on Next.js side. https://www.loom.com/share/150deedd25a24259b0aa8cb141cec1d3 The redirects now go through Netlify since it's a lot more flexible, and we need to do that later when porting Next.js to Netlify, etc. ## Not done / follow-up: Other pages and UI components that use `<Link>` to a doc page need to check against `NEXT_PUBLIC_ASTRO_URL` and make sure to use the updated `/docs` path for that. I only handled the homepage for now just to show it working. (cherry picked from commit 1976d56)
feat(graph): task graph support multiple targets (nrwl#32418) - [x] graph-client supports multiple targets with multiselect and query params `?targets` - [x] `nx graph` supports multiple targets (i.e: `nx run-many -t build,test --graph` <img width="277" height="385" alt="image" src="https://github.com/user-attachments/assets/6869b652-2ecb-4afb-9ae5-ec29628afec1" />
PreviousNext