[pull] master from nrwl:master #31
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<!-- 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 #
Commented out `WebinarNotifier` and all instances of the live event banner in hero components across the project.
Update tagline.
This PR removes the `/nx-api` pages from `nx-dev`. They are already redirected from `/nx-api` to either `/technologies` or `/reference/core-api` URLs. e.g. `/nx-api/nx` goes to `/reference/core-api/nx` and `/nx-api/react` goes to `/technologies/react/api` **Changes**: - Remove old `nx-api.json` from being generated in `scripts/documentation/generators/generate-manifests.ts` -- this was used to generate the sitemap - Remove `pages/nx-api` from Next.js app since we don't need them - Remove workaround from link checker `scripts/documentation/internal-link-checker.ts` -- the angular rspack/rsbuild and other workarounds are gone now that they are proper docs in `map.json` - Update Powerpack/Remote Cache reference docs to exclude API documents (since they are duplicated in the Intro page) -- `nx-dev/models-document/src/lib/mappings.ts` - All content in `docs` have been updated with new URL structure **Note:** Redirects are already handled, and Claude Code was used to verify the updated `docs/` URLs (see report below). The twelve 404s links were updated by hand. ## Verification Report https://gist.github.com/jaysoo/c7863fe7e091cb77929d1976165c357a
This PR improves our Docker support by sanitizing project names for compatibility with Docker commands and Linux systems. closes: #31421
## Current Behavior Conformance is broken ## Expected Behavior Conformance is not broken...or just doesn't run so we can't tell it's broken
## Current Behavior In ng-packagr-lite watch mode, all output files are written to disk on every incremental build regardless of whether their content actually changed. This causes downstream watchers (like Vite) to see all files as "changed" and trigger full rebuilds instead of incremental ones. ## Expected Behavior Only files with changed content should be written to disk during incremental builds in watch mode. This allows downstream watchers to properly detect which files actually changed and perform efficient incremental rebuilds. ## Related Issue(s) Fixes #31033 🤖 Generated with [Claude Code](https://claude.ai/code)
<!-- 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 #
This PR adds the missing `tui` property in `nx.json` on this page: https://nx.dev/reference/nx-json <img width="884" alt="Screenshot 2025-06-04 at 1 10 04 PM" src="https://github.com/user-attachments/assets/d7edb8dd-7b1a-4e3e-a738-4eb0dbb1feba" /> Preview: https://nx-dev-git-docs-add-tui-option-nrwl.vercel.app/reference/nx-json
This pull request introduces several updates to the CI/CD workflows and matrix configuration files. The aim is to highlight critical Nx failures contained in each project for maintainers to address. ### Changes - Improvements to workflow caching. - Improvements to macOS simulator handling. - Updates to Slack notifications. - Update matrix data processing for golden projects. - Support for Windows has been temporarily disabled due to build issues.
…nspiler (#31469) ## Current Behavior When creating a `ts-node` transpiler, only `compilerOptions` are provided. Because we instruct `ts-node` to skip reading the tsconfig (this was previously done to avoid some edge cases), other options in the tsconfig files are lost (e.g. `ts-node` specific options). This was previously reported at #21695 and fixed by #21723, but a rework at a later point caused a regression. ## Expected Behavior When creating a `ts-node` transpiler, we should provide `compilerOptions` and the `ts-node` options.
…nd add missing redirects (#31473) This PR fixes some 404s in the production nx.dev docs. These were picked up by the script provided here: https://linear.app/nxdev/issue/NXC-2628/create-a-test-for-verifying-the-redirect-rules ``` https://nx.dev/nx-api → Status: 404 https://nx.dev/nx-api/azure-cache/documents/overview → Status: 404 https://nx.dev/nx-api/owners/documents/overview → Status: 404 https://nx.dev/nx-api/gcs-cache/documents/overview → Status: 404 https://nx.dev/nx-api/s3-cache/documents/overview → Status: 404 https://nx.dev/nx-api/shared-fs-cache/documents/overview → Status: 404 https://nx.dev/nx-api/angular-rspack/documents/create-config → Status: 404 https://nx.dev/nx-api/angular-rspack/documents/create-server → Status: 404 https://nx.dev/nx-api/angular-rsbuild/documents/create-config → Status: 404 https://nx.dev/nx-api/angular-rsbuild/documents/create-server → Status: 404 https://nx.dev/nx-api/angular-rspack/documents → Status: 404 https://nx.dev/nx-api/angular-rsbuild/documents → Status: 404 10000 https://nx.dev/nx-api/angular-rspack/executors → Status: 404 https://nx.dev/nx-api/angular-rsbuild/executors → Status: 404 https://nx.dev/nx-api/angular-rspack → Status: 404 https://nx.dev/nx-api/angular-rsbuild → Status: 404 https://nx.dev/nx-api/angular-rspack/migrations → Status: 404 https://nx.dev/nx-api/angular-rsbuild/migrations → Status: 404 https://nx.dev/nx-api/angular-rspack/generators → Status: 404 https://nx.dev/nx-api/angular-rsbuild/generators → Status: 404 ``` **Changes:** - The `/nx-api` goes to `/plugin-registry` since the intend is to list out plugins. - Remote Cache and Owners do not have overview API doc since this is now a proper overview page (e.g. `/reference/core-api/azure-cache/overview` NOT `/reference/core-api/azure-cache/api/documents/overview` - Angular Rspack and Rsbuild had missing API docs that did not get ported
<!-- 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 --> Currently, if you try to import a ESM lib after you generate a Next.js application it fails to build due to how the module exports `export * from './lib/lib8446520.js';`. This has been addressed with webpack and needs to be extended to Next.js. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> You should work out of the box and you should be able to import a lib defined like: `export * from './lib/lib8446520.js';.` ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> This is also related to our webpack and rspack packages. Changes have also been made to them to ensure consistency across bundlers. Fixes #30714
This PR updates the CI workflow in `.github/workflows/ci.yml` to improve the setup and management of iOS simulators. The change includes - Enhanced error handling - Better diagnostics - Configurations for M-series Macs. This change is similar to what we in `.github/workflows/e2e-matrix.yml` so the result should be consistent across workflows.
This was broken in #29691 it's missing this return.
) ## Current Behavior Currently, ndcunningham is not included in the list of authorized users who can trigger the Claude AI assistant in GitHub workflows. ## Expected Behavior With this change, ndcunningham will be able to trigger the Claude AI assistant by mentioning @claude in GitHub issue comments, PR comments, and PR reviews. ## Related Issue(s) This change adds ndcunningham to the authorized user list for the Claude workflow, enabling them to use the AI assistant for development tasks.
…ow multi-level group dependencies (#31374)
…#31483) <!-- 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 --> Node 24 is more strict for module resolution and was not able to resolve this path. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Node 24 is now able to resolve this path. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
Add support for Angular v20. BREAKING CHANGE: Support for Angular v17 was dropped. ### TODO - [x] Update Angular packages to the stable v20 - [x] Update `jest-preset-angular` when it releases support for Angular v20 - [x] PR: thymikee/jest-preset-angular#3119 - [x] Release: https://github.com/thymikee/jest-preset-angular/releases/tag/v14.6.0 - [ ] Update Angular ESLint packages to the v20 stable version once released - [ ] PR: angular-eslint/angular-eslint#2448 - [x] Update AnalogJS packages when they are released with support for Angular v20 - [x] PR: analogjs/analog#1751 - [x] Release: https://github.com/analogjs/analog/releases/tag/v1.17.0 - [x] Fix for `@analogjs/vitest-angular` peer deps: analogjs/analog#1754 - [x] Release: - [x] Beta: https://github.com/analogjs/analog/releases/tag/v1.17.1-beta.1 - [x] Stable: https://github.com/analogjs/analog/releases/tag/v1.17.1 - [ ] Update Storybook packages - [x] PRs: storybookjs/storybook#31602 and storybookjs/storybook#31611 - [x] Storybook 9 Release: https://github.com/storybookjs/storybook/releases/tag/v9.0.3 - [ ] Storybook 8 Release??: PENDING - [ ] Remaining issue: storybookjs/storybook#31652
<!-- 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 --> Running tests in the Cursor terminal fails. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> Running tests in the Cursor terminal should pass. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
## Current Behavior We currently do not have support for Storybook 9, nor any migrations to help users switch to it. ## Expected Behavior Support Storybook 9 and add a migration for users to switch to v9 BREAKING CHANGE: Remove deprecated generators: `@nx/storybook:cypress-project`, `@nx/react-native:storybook-configuration`, `@nx/react-native:stories`, `@nx/react-native:component-story`
…support nested projects (#31488) ## Current Behavior When running the `lint` task on a project that contains nested projects, the task runs over all the files, including the ones inside the nested projects, but the task cache status is not affected by changes to the files in nested projects. This only happens when the inputs are defined with `{projectRoot}/...` (what the `@nx/eslint/plugin` infers). The `{projectRoot}` token scopes the files inside the project without files in other nested projects. While the `{workspaceRoot}` token would include every file and wouldn't scope them to any particular project. ## Expected Behavior The `@nx/eslint/plugin` should infer `lint` tasks with their inputs using the `{workspaceRoot}` token to support nested projects. This would be more aligned with what the tool itself does, which runs over all the files inside the project root regardless of them being inside nested Nx projects. Additionally, the difference in behavior between `{workspaceRoot}` and `{projectRoot}` should be documented. ## Related Issue(s) Fixes #31264
… and improved logging (#31462) ## Current Behavior Currently, IDE integration setup requires manual configuration and lacks streamlined auto-installation capabilities for Nx Console. The logging system also needs improvement for better developer experience. ## Expected Behavior With these changes, the IDE integration provides: - Prompt for automatic Nx Console installation with user preferences - Enhanced native logger with proper formatting and levels - Better development documentation for IDE setup - Updated documentation links to use the new format ## Related Issue(s) <\!-- Please link the issue being fixed so it gets closed when this is merged. --> This PR implements IDE integration improvements including Nx Console auto-installation and enhanced logging capabilities.
…g the graph (#31455) ## Current Behavior When using Node.js subpath imports with the same name in different projects, the Nx graph incorrectly picks up seemingly random dependencies between projects that shouldn't exist. This happens because the result of the resolution performed with TypeScript is cached using the import path as the cache key. The problem with that is that multiple projects can have the same subpath import name pointing to internal files of the project, so when the resolution is made for the first project (say `project1`), the result will be cached and incorrectly reused for other projects with the same subpath import name. So, all projects with the same subpath import name would resolve the dependency to the first project (`project1`). The same could happen to projects with TS path mappings defined in the project's tsconfig file. These TS path mappings would only apply to the project internally and therefore, other unrelated projects could also define them with the same name pointing to different files. ## Expected Behavior The Node.js subpath imports should be handled correctly. The TypeScript resolution result should be cached safely and scoped to the project from which the import is being done. ## Related Issue(s) Fixes #31223
…ort (#31490) ## Current Behavior The `nx report` command uses tab characters for indenting local workspace plugins in its output, which creates inconsistent formatting compared to other sections like 'Registered Plugins' and 'Community plugins'. ## Expected Behavior Local workspace plugins should be formatted consistently with other plugin sections in the report output, without tab indentation. ## Related Issue(s) This is a minor formatting improvement for better consistency in the nx report output. No specific issue was filed for this change.
## Current Behavior The Angular ESLint packages are installed with a v20 beta version. ## Expected Behavior The Angular ESLint packages should be installed with the stable v20 version.
Refined AI features including new capabilities (self-healing CI, AI data analysis), updated descriptions, and rearranged feature order. Adjusted section ID for CI security and added links to highlight AI integrations in pricing plans.
…ion (#31671) ## Changes - Update build output path from {workspaceRoot}/dist/{projectRoot} to .next folder - Replace vite.config.ts example with next.config.js distDir configuration - Add note about legacy executor configuration vs inferred tasks - Clarify that sourceRoot may not exist in all Next.js projects 🤖 Generated with [Claude Code](https://claude.ai/code) <!-- 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 The docs for Next.js says output can be configured in `vite.config.ts`, which is nonsense. It also mentions the output directory that is only applicable in the legacy setup. ## Expected Behavior Fix configuration example, and show different ways to configure output (both new crystal setup, and legacy executor-based setup). ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #31037 Co-authored-by: Claude <noreply@anthropic.com>
Update React monorepo tutorial: - Fix reference to .eslintrc.base.json (now eslint.config.mjs) 🤖 Generated with [Claude Code](https://claude.ai/code) <!-- 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 #30199 Co-authored-by: Claude <noreply@anthropic.com>
This PR updates our `e2e-js` test to include dependencies for all package managers and not just pnpm. E2E Matrix for `e2e-js` is now passing: https://github.com/nrwl/nx/actions/runs/15786673606/job/44504580439
Update callout type from 'warn' to 'warning' in CVE blog post.
The simpleName option is no longer useful as we've moved to using options "as provided" without transformation. Users should provide the exact name, directory, and import path they want to use. ## Changes - Add x-deprecated to schema.json marking for removal in Nx 22 - Add runtime warning when simpleName is used 🤖 Generated with [Claude Code](https://claude.ai/code) <!-- 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 Users are confused with `--simpleName` with using `--name` AND `--directory` ## Expected Behavior We should tell users that only `--name` should be used. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #29508 --------- Co-authored-by: Claude <noreply@anthropic.com>
#31664) ## Description This PR fixes an issue where asset files copied during a build using the `@nx/js:tsc` executor are placed in the wrong directory depending on the current working directory from which the `nx` command is executed. This behavior becomes particularly problematic in scenarios like release workflows that rely on `preVersionCommand` to run E2E tests. For instance, when using tools like Jest from the root of an E2E project, scripts like `start-local-registry` may trigger a build and run the `preVersionCommand`. However, instead of placing assets in the expected `dist` folder of the project, they are incorrectly copied relative to the E2E folder’s location. ## Reproduction Steps 1. Create a new Nx workspace: ```bash npx --yes create-nx-workspace assets-issue --preset=ts --no-interactive cd assets-issue ``` 2. Add the Nx Plugin package: ```bash nx add @nx/plugin ``` 3. Generate a new plugin: ```bash nx g @nx/plugin:plugin packages/my-plugin --linter eslint --unitTestRunner jest ``` 4. Add a generator to the plugin: ```bash nx g @nx/plugin:generator packages/my-plugin/src/generators/my-generator ``` 5. Build the plugin from the workspace root: ```bash nx build my-plugin ``` ✅ Assets are copied correctly: ``` dist/packages/my-plugin/generators/files/src/index.ts.template dist/packages/my-plugin/generators/schema.json dist/packages/my-plugin/generators/schema.d.ts ``` 6. Now build the same project from a nested folder: ```bash mkdir e2e && cd e2e nx build my-plugin --skip-nx-cache ``` ❌ Assets are copied relative to the current folder: ``` e2e/packages/my-plugin/dist/generators/files/src/index.ts.template e2e/packages/my-plugin/dist/generators/schema.json e2e/packages/my-plugin/dist/generators/schema.d.ts ``` ## Expected Behavior The build output—especially copied assets—should always respect the project’s `outputPath` configuration regardless of where the `nx` command is invoked from. The behavior should be consistent and **not influenced by `process.cwd()`**.
Co-authored-by: Juri <juri.strumpflohner@gmail.com>
people use it locally with different ports so we should just add it to gitignore
Created a new contact page for Nx Labs to highlight services and provide a form for inquiries. Updated the professional services section in the header menu to include a link to this page.
add docs over polygraph features https://nx-dev-git-docs-polygraph-nrwl.vercel.app/ci/recipes/enterprise/polygraph --------- Co-authored-by: Mike Hartington <mhartington@users.noreply.github.com> Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by: Mike Hartington <mikehartington@gmail.com>
## Current Behavior In the new TS Soln Setup with Package Manager Workspaces, there is currently no builtin method for creating a pruned lockfile that is agnostic across bundlers and compilers. This is problematic for apps that must be containerized. ## Expected Behavior Add a new `@nx/js:prune-lockfile` executor that can be used to produce a pruned lockfile in the build artifact output directory, ready for containerization. --------- Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> Co-authored-by: Colum Ferry <Coly010@users.noreply.github.com>
…0.15.0 to fix vulnerability (#30806) ## Current Behavior `@module-federation/enhanced` v0.9.0 has a dependency to `@module-federation/dts-plugin` v0.9.0, which has a dependency to `koa` v2.15.4, which has a [security vulnerability ](GHSA-x2rg-q646-7m2v) And because `@module-federation/enhanced` is pinned with `^0.9.0` it won't automatically update it to a version greater than `0.9.x` ## Expected Behavior Until `@module-federation/enhanced` releases a v1, it needs to be manually updated when we want to benefit from a newer "minor" version. Pinning `@module-federation/enhanced` to `^0.15.0` allows to benefit from the latest release and security fix. ## Related Issue(s) Fixes #30502 Fixes #30748 --------- Co-authored-by: Colum Ferry <cferry09@gmail.com>
…pace root (#31698) ## Current Behavior When users provide an absolute path for the Module Federation manifest file that already includes the workspace root, the plugin incorrectly prepends the workspace root again, resulting in an invalid path like `/workspace/root/workspace/root/path/to/manifest.json`. ## Expected Behavior The plugin should detect if the provided manifest file path already starts with the workspace root and avoid prepending it again. This allows users to provide either relative or absolute paths for the manifest file, and both will work correctly. ## Related Issue(s) Fixes #31524
… composables (#31701) - Modified create-ts-config.ts to make tsconfig.json extend ./.nuxt/tsconfig.json instead of root tsconfig - Updated nuxt.config.ts template to make .nuxt/tsconfig.json extend the root tsconfig with correct relative path - Added relativePathToRootTsConfig parameter to template generation - Updated test snapshots to reflect the new configuration chain This ensures IDEs can properly recognize Nuxt components, composables, and auto-imports by establishing the correct TypeScript configuration inheritance chain: tsconfig.app.json → tsconfig.json → .nuxt/tsconfig.json → tsconfig.base.json ## Related Issues #30742 Co-authored-by: Claude <noreply@anthropic.com>
…o remove confusion (#31707) ## Current Behavior Documentation examples show `tsconfig.lib.json` and `tsconfig.spec.json` extending from `./tsconfig.json`. ## Expected Behavior Examples should extend directly from `../../tsconfig.base.json` to match Nx's recommended TypeScript configuration structure. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #31704
…n JSX transform (#31705) This PR fixes and issue with Next.js + Jest to remove warnings about outdated transforms. ## Changes Made - Updated Next.js application generator to use next/jest.js instead of manual babel-jest configuration - Updated Next.js library generator to use the same modern configuration approach - Added e2e tests to verify the new Jest configuration works correctly - Kept same CJS vs ESM logic for JS vs TS config (existing behavior) ## Current Behavior When using React 19 with Next.js applications in Nx, developers receive a warning about outdated JSX transform because the Jest configuration uses manual babel-jest setup instead of Next.js's recommended approach. ## Expected Behavior Next.js applications and libraries generated by Nx should use next/jest.js configuration which automatically handles the modern JSX transform (runtime: 'automatic') and provides proper Jest setup for Next.js projects without warnings. ## Related Issue(s) Fixes #27900
https://nx-dev-git-philip-polygraph-release-article-nrwl.vercel.app/blog/nx-cloud-introducing-polygraph --------- Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
…ths plugin (#31729) ## Current Behavior The `nxViteTsPaths` plugin determines the buildable libraries by checking the existence of the following target: ```ts process.env.NX_TASK_TARGET_TARGET === 'serve' ? 'build' : process.env.NX_TASK_TARGET_TARGET ``` But it later creates the command to build the dependencies to always run the `process.env.NX_TASK_TARGET_TARGET` target. This is wrong and results in trying to run the `serve` task for the dependencies when the root task is `serve`. ## Expected Behavior The `nxViteTsPaths` plugin should use the same task name to determine the buildable libraries and run the command to build the dependencies. ## Related Issue(s) Fixes #31333
…31670) <!-- 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 adds new partners `Angular Architects` and `This Dot Labs` ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
Add callout box to the inputs documentation explaining that .gitignored files are automatically excluded from inputs and won't affect task hash computation. Fixes #31574 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Jason Jean <FrozenPandaz@users.noreply.github.com>
…on stopping functionality. (#31626) ## Overview This PR enhances the Migrate UI by adding a "Stop" button that allows users to halt in-progress migrations at any point during execution. It works in tandem with nrwl/nx-console#2567 ### Currently When a migration is running and needs to be stopped for any reason: - User accidentally triggered the migration - Migration is taking longer than expected - Changes are needed before completion Users must wait for the migration to complete before using the available "Undo" or "Skip" options. ### Expected Users should be able to stop a currently running migration at any time before it completes, providing immediate control over the migration process. ### Key Features: - Refactor guards to improve migration state checks and add conditions for running and completing migrations. - Update the state machine to handle new states for running, stopped, and evaluating migrations. - Implement logic to track running migrations and allow for stopping them gracefully. - Introduce a new process for running migrations in a separate child process to support cancellation. - Enhance metadata management to include stopped migrations and update UI accordingly. (The UI is completely driven by the backend now aka Nx Console) - Add tests to cover new migration states and behaviours.
…ederation remotes (#31723) ## Current Behavior Module federation configurations with relative URLs are broken due to PR #30615, which forced all remote URLs to be parsed as absolute URLs using `new URL()`. This breaking change prevents developers from using relative URLs in their module federation setups, causing runtime errors when the application tries to load remote modules. ## Expected Behavior Module federation should support both relative and absolute URLs seamlessly: - Relative URLs should work as they did before, maintaining backward compatibility - Absolute URLs should continue to work with enhanced query parameter support - The URL processing should be consistent across all module federation helpers (Angular and React) ## Related Issue(s) Fixes #31538
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.1)
Can you help keep this open source service alive? 💖 Please sponsor : )