Bump the nestjs group across 1 directory with 2 updates#109
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Bump the nestjs group across 1 directory with 2 updates#109dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
a2dd7f2 to
65bcfaa
Compare
3 tasks
keysersoft
added a commit
that referenced
this pull request
May 10, 2026
Backend declared rxjs as ^7.8.1, but several @nestjs/cli transitive deps (@angular-devkit/*) pin rxjs to exact 7.8.1, while the rest of the @nestjs ecosystem resolves to 7.8.2. With certain bumps (e.g. the @nestjs/cli 11.0.21 group in PR #109), npm decides to install a second rxjs at packages/backend/node_modules/rxjs, breaking typecheck with 'Observable from two different rxjs' errors because the backend ends up with two rxjs instances at different paths. Pinning rxjs in backend to the exact 7.8.2 used by the @nestjs/common, @nestjs/core, etc. ecosystem forces npm to dedupe to a single root copy. The @Angular-devkit nested 7.8.1 copies remain but are isolated to nest-cli tooling and never reach the backend's compiled code.
7f65b55 to
3c00363
Compare
keysersoft
added a commit
that referenced
this pull request
May 10, 2026
Backend declared rxjs as ^7.8.1, but several @nestjs/cli transitive deps (@angular-devkit/*) pin rxjs to exact 7.8.1, while the rest of the @nestjs ecosystem resolves to 7.8.2. With certain bumps (e.g. the @nestjs/cli 11.0.21 group in PR #109), npm decides to install a second rxjs at packages/backend/node_modules/rxjs, breaking typecheck with 'Observable from two different rxjs' errors because the backend ends up with two rxjs instances at different paths. Pinning rxjs in backend to the exact 7.8.2 used by the @nestjs/common, @nestjs/core, etc. ecosystem forces npm to dedupe to a single root copy. The @Angular-devkit nested 7.8.1 copies remain but are isolated to nest-cli tooling and never reach the backend's compiled code.
3c00363 to
450926c
Compare
keysersoft
added a commit
that referenced
this pull request
May 10, 2026
Backend declared rxjs as ^7.8.1, but several @nestjs/cli transitive deps (@angular-devkit/*) pin rxjs to exact 7.8.1, while the rest of the @nestjs ecosystem resolves to 7.8.2. With certain bumps (e.g. the @nestjs/cli 11.0.21 group in PR #109), npm decides to install a second rxjs at packages/backend/node_modules/rxjs, breaking typecheck with 'Observable from two different rxjs' errors because the backend ends up with two rxjs instances at different paths. Pinning rxjs in backend to the exact 7.8.2 used by the @nestjs/common, @nestjs/core, etc. ecosystem forces npm to dedupe to a single root copy. The @Angular-devkit nested 7.8.1 copies remain but are isolated to nest-cli tooling and never reach the backend's compiled code.
Bumps the nestjs group with 2 updates in the / directory: [@nestjs/cli](https://github.com/nestjs/nest-cli) and [@nestjs/testing](https://github.com/nestjs/nest/tree/HEAD/packages/testing). Updates `@nestjs/cli` from 11.0.16 to 11.0.21 - [Release notes](https://github.com/nestjs/nest-cli/releases) - [Commits](nestjs/nest-cli@11.0.16...11.0.21) Updates `@nestjs/testing` from 11.1.14 to 11.1.19 - [Release notes](https://github.com/nestjs/nest/releases) - [Commits](https://github.com/nestjs/nest/commits/v11.1.19/packages/testing) --- updated-dependencies: - dependency-name: "@nestjs/cli" dependency-version: 11.0.21 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: nestjs - dependency-name: "@nestjs/testing" dependency-version: 11.1.19 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: nestjs ... Signed-off-by: dependabot[bot] <support@github.com>
450926c to
1078ce1
Compare
3 tasks
keysersoft
added a commit
that referenced
this pull request
May 10, 2026
* Force rxjs to 7.8.1 across workspace via root override Follow-up to the previous rxjs pin (7.8.2): with the @nestjs/cli 11.0.21 bump in PR #109, npm hoists rxjs 7.8.1 at the root because the bumped @angular-devkit/* (transitive of nest-cli) hard-pins rxjs to 7.8.1. Backend pinned to 7.8.2 then ends up with a nested rxjs at packages/backend/node_modules/rxjs, reproducing the duplicate-Observable typecheck error. Pinning backend to 7.8.1 and adding a root override 'rxjs: 7.8.1' aligns backend with the angular-devkit-driven root resolution. The remaining @nestjs ecosystem also accepts 7.8.1 (their range is ^7.8.0 or wider). After this change npm hoists a single rxjs at root; nested copies in @angular-devkit/concurrently/@nestjs/schematics remain but are isolated to those tools' internals and never collide with backend types. * Regenerate lockfile after rxjs override * Pin eslint-plugin-react-hooks to 7.0.1 alongside rxjs override Regenerating the lockfile to apply the rxjs override also bumped eslint-plugin-react-hooks transitively from 7.0.1 to 7.1.1 (via eslint-config-next), which introduced a new 'use-before-define' rule that flags two pre-existing patterns in the frontend (connectors/store/page.tsx and settings/license/page.tsx). Pinning the plugin to 7.0.1 keeps the lockfile aligned with main's behaviour; the new rule can be addressed in a separate PR.
Contributor
|
@dependabot rebase |
Contributor
Author
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
Contributor
|
@dependabot recreate |
Contributor
Author
|
Looks like these dependencies are no longer updatable, so this is no longer needed. |
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
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.
Bumps the nestjs group with 2 updates in the / directory: @nestjs/cli and @nestjs/testing.
Updates
@nestjs/clifrom 11.0.16 to 11.0.21Release notes
Sourced from @nestjs/cli's releases.
... (truncated)
Commits
07cdd40chore(): release v11.0.21255a559fix: revert #3315 due to #3390cc0e745chore(): release v11.0.20705bb7dfix: revert #3313 due to #3391 and #339076a8e0dMerge pull request #3266 from nestjs/renovate/swc-monorepo8496c76chore(deps): update swc monorepocf6d610Merge pull request #3346 from yogeshwaran-c/fix/swc-watcher-ignored-filterfcdc934Merge pull request #3347 from yogeshwaran-c/fix/assets-manager-close-watchers...299d724Merge pull request #3350 from yogeshwaran-c/test/remaining-flagsdd78c4aMerge pull request #3372 from nestjs/renovate/prettier-3.xUpdates
@nestjs/testingfrom 11.1.14 to 11.1.19Release notes
Sourced from @nestjs/testing's releases.
... (truncated)
Commits
6730995chore(release): publish v11.1.19 release3c1cc5fchore(release): publish v11.1.18 release5a05f52chore: update readme447a373chore(release): publish v11.1.17 release315e698chore(release): publish v11.1.16 release6add3d6chore(release): publish v11.1.15 release