nx · Issues· 504 open

@nx/esbuild:esbuild resolves tsConfig relative to current working directory

`nx release`: regressions with independent projects relationship

nx release: per-group changelog files not staged into release commit when using --groups with fixed projectsRelationship

nx release changelog: re-rendering an existing version never replaces the entry when versionTitleDate is enabled

nx release: projectChangelogs.createRelease on a fixed release group creates one remote release per project on the same tag (last body wins)

nx release: dependent traversal continues through an excluded dependent, pulls a fixed release group in partially, then fails with "no current version resolved"

nx release version does not propagate changes to release groups with "projectsRelationship": "fixed"

@nx/esbuild: --output-path CLI override is ignored for the bundled entry file (getOutfile uses context.target.options.outputPath instead of normalized options)

Local cache restore copies outputs one file at a time: 61 s for 77,642 files on a Windows laptop whose disk is 6% busy

Daemon re-copies unchanged cached outputs after a restore: late watcher events and rescans drop recorded output hashes

Hot reload stopped working

maven.config is not read with the new maven executor

angular-rspack: Dev server rebuild doesn't reflect code changes on server part

Exploring a modern Nx-native NestJS v12 plugin aligned with Nest CLI and Project Crystal

nx.json should support parallel as a percentage to be consistent with cli arg