Update @nestjs/cli 10.1.17 → 10.1.18 (patch)
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳ ️ @nestjs/cli (10.1.17 → 10.1.18) · Repo
Release Notes
10.1.18
- Merge pull request #2244 from eabrouwer3/eb/2242-json-cli-option (e2e046f)
- Merge pull request #2260 from nestjs/renovate/typescript-5.x (484d20a)
- Merge pull request #2270 from nestjs/renovate/angular-cli-monorepo (4125cb9)
- Merge pull request #2277 from nestjs/renovate/cimg-node-20.x (81476d9)
- Merge pull request #2281 from dotlambda/fsevents-1.2.13 (2e73b9d)
- Merge pull request #2294 from micalevisk/refactor/issue-2275 (197b30f)
- fix(deps): update angular-cli monorepo to v16.2.3 (b76513e)
- chore(deps): update dependency @types/node to v18.17.18 (b33b2af)
- chore(deps): update node.js to v20.7 (a819fa4)
- chore(deps): update dependency @swc/core to v1.3.86 (2d4bce0)
- chore(deps): update typescript-eslint monorepo to v6.7.2 (4050bd1)
- style: fix formatting (6d1caf2)
- perf: cache loaded configuration file (1 vs 2/3 calls) (8e2e4c0)
- chore(deps): update dependency @types/node to v18.17.17 (66b8a8d)
- chore(deps): update dependency @types/webpack-node-externals to v3.0.1 (5cef675)
- chore(deps): update dependency @types/jest to v29.5.5 (2429bbd)
- chore(deps): update dependency @types/node to v18.17.16 (6e110f9)
- chore(deps): update dependency @swc/core to v1.3.85 (2b71927)
- chore(deps): update dependency jest to v29.7.0 (88ed13d)
- chore(deps): update typescript-eslint monorepo to v6.7.0 (6576ca9)
- chore(deps): update dependency @swc/core to v1.3.84 (91f96d3)
- chore(deps): update fsevents to 1.2.13 (a0dbd08)
- chore(deps): update dependency eslint to v8.49.0 (7d6efc4)
- chore(deps): update dependency @types/node to v18.17.15 (1f94cab)
- chore(deps): update dependency @swc/core to v1.3.83 (3e23e94)
- chore(deps): update typescript-eslint monorepo to v6.6.0 (f59d865)
- chore(deps): update dependency @types/node to v18.17.14 (802a73c)
- chore(deps): update dependency @types/node to v18.17.13 (3229398)
- chore(deps): update dependency @swc/core to v1.3.82 (96e110b)
- fix(deps): update dependency typescript to v5.2.2 (7b4086f)
- fix: Prevent need for double escaping strings (519030c)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 30 commits:
chore(): release v10.1.18
Merge pull request #2244 from eabrouwer3/eb/2242-json-cli-option
Merge pull request #2260 from nestjs/renovate/typescript-5.x
Merge pull request #2270 from nestjs/renovate/angular-cli-monorepo
Merge pull request #2277 from nestjs/renovate/cimg-node-20.x
Merge pull request #2281 from dotlambda/fsevents-1.2.13
Merge pull request #2294 from micalevisk/refactor/issue-2275
fix(deps): update angular-cli monorepo to v16.2.3
chore(deps): update dependency @types/node to v18.17.18
chore(deps): update node.js to v20.7
chore(deps): update dependency @swc/core to v1.3.86
chore(deps): update typescript-eslint monorepo to v6.7.2
style: fix formatting
perf: cache loaded configuration file (1 vs 2/3 calls)
chore(deps): update dependency @types/node to v18.17.17
chore(deps): update dependency @types/webpack-node-externals to v3.0.1
chore(deps): update dependency @types/jest to v29.5.5
chore(deps): update dependency @types/node to v18.17.16
chore(deps): update dependency @swc/core to v1.3.85
chore(deps): update dependency jest to v29.7.0
chore(deps): update typescript-eslint monorepo to v6.7.0
chore(deps): update dependency @swc/core to v1.3.84
chore(deps): update fsevents to 1.2.13
chore(deps): update dependency eslint to v8.49.0
chore(deps): update dependency @types/node to v18.17.15
chore(deps): update dependency @swc/core to v1.3.83
chore(deps): update typescript-eslint monorepo to v6.6.0
chore(deps): update dependency @types/node to v18.17.14
chore(deps): update dependency @types/node to v18.17.13
chore(deps): update dependency @swc/core to v1.3.82
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase
.
All Depfu comment commands
- @depfu rebase
- Rebases against your default branch and redoes this update
- @depfu recreate
- Recreates this PR, overwriting any edits that you've made to it
- @depfu merge
- Merges this PR once your tests are passing and conflicts are resolved
- @depfu cancel merge
- Cancels automatic merging of this PR
- @depfu close
- Closes this PR and deletes the branch
- @depfu reopen
- Restores the branch and reopens this PR (if it's closed)
- @depfu pause
- Ignores all future updates for this dependency and closes this PR
- @depfu pause [minor|major]
- Ignores all future minor/major updates for this dependency and closes this PR
- @depfu resume
- Future versions of this dependency will create PRs again (leaves this PR as is)