nest
nest copied to clipboard
chore(deps): update dependency webpack to v5.90.2
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| webpack | 5.89.0 -> 5.90.2 |
Release Notes
webpack/webpack (webpack)
v5.90.2
Bug Fixes
- use
Math.imulinfnv1a32to avoid loss of precision, directly hash UTF16 values - the
setStatus()of the HMR module should not return an array, which may cause infinite recursion __webpack_exports_info__.xxx.canMangleshouldn't always same as default- mangle export with destructuring
- use new runtime to reconsider skipped connections
activeState - make dynamic import optional in
try/catch - improve auto publicPath detection
Dependencies & Maintenance
- improve CI setup and include Node.js@21
v5.90.1
Bug Fixes
- set
unmanagedPathsin defaults - correct
preOrderIndexandpostOrderIndex - add fallback for MIME mismatch error in async wasm loading
- browsers versions of ECMA features
Performance
- optimize
compareStringsNumeric - optimize
numberHashusing 32-bit FNV1a for small ranges, 64-bit for larger - reuse VM context across webpack magic comments
v5.90.0
Bug Fixes
- Fixed inner graph for classes
- Optimized
RemoveParentModulesPluginvia bigint arithmetic - Fixed worklet detection in production mode
- Fixed an error for cyclic importModule
- Fixed types for
ServerandDirent - Added the
fetchPriorityto hmr runtime'sensureChunkfunction - Don't warn about dynamic import for build dependencies
- External module generation respects the
output.environment.arrowFunctionoption - Fixed consumimng shared runtime module logic
- Fixed a runtime logic of multiple chunks
- Fixed destructing assignment of dynamic import json file
- Passing errors array for a module hash
- Added
/*#__PURE__*/to generatedJSON.parse() - Generated a library manifest after clean plugin
- Fixed non
amdexternals andamdlibrary - Fixed a bug in
SideEffectsFlagPluginwith namespace re-exports - Fixed an error message for condition
or - The
strictModuleErrorHandlingis now working - Clean up child compilation chunk graph to avoid memory leak
- [CSS] - Fixed CSS import prefer relative resolution
- [CSS] - Fixed CSS runtime chunk loading error message
New Features
- Allow to set
falsefor dev server inwebpack.config.js - Added a warning for async external when not supported
- Added a warning for async module when not supported
- Added the
node-moduleoption for thenode.__filename/__dirnameand enable it by default for ESM target - Added the
snapshot.unmanagedPathsoption - Exposed the
MultiCompilerOptionstype - [CSS] - Added CSS parser options to enable/disable named exports
- [CSS] - Moved CSS the
exportsOnlyoption to CSS generator options
Dependencies & Maintenance
- use node.js LTS version for lint
- bump actions/cache from 3 to 4
- bump prettier from 3.2.1 to 3.2.3
- bump assemblyscript
- bump actions/checkout from 3 to 4
Full Changelog: https://github.com/webpack/webpack/compare/v5.89.0...v5.90.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
âš Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
â™» Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: sample/31-graphql-federation-code-first/users-application/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR! reflect-metadata@"0.2.1" from the root project
npm ERR! peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR! @nestjs/common@"10.3.2" from the root project
npm ERR! peer @nestjs/common@"^9.3.8 || ^10.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/apollo
npm ERR! @nestjs/apollo@"12.0.11" from the root project
npm ERR! 5 more (@nestjs/core, @nestjs/graphql, @nestjs/mapped-types, ...)
npm ERR! 1 more (@nestjs/core)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/graphql
npm ERR! @nestjs/graphql@"12.0.11" from the root project
npm ERR! peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/apollo
npm ERR! @nestjs/apollo@"12.0.11" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/graphql
npm ERR! @nestjs/graphql@"12.0.11" from the root project
npm ERR! peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/apollo
npm ERR! @nestjs/apollo@"12.0.11" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-18T08_51_56_925Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-18T08_51_56_925Z-debug-0.log
File name: sample/31-graphql-federation-code-first/gateway/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR! reflect-metadata@"0.2.1" from the root project
npm ERR! peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/common
npm ERR! @nestjs/common@"10.3.2" from the root project
npm ERR! peer @nestjs/common@"^9.3.8 || ^10.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/apollo
npm ERR! @nestjs/apollo@"12.0.11" from the root project
npm ERR! 5 more (@nestjs/core, @nestjs/graphql, @nestjs/mapped-types, ...)
npm ERR! 1 more (@nestjs/core)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/graphql
npm ERR! @nestjs/graphql@"12.0.11" from the root project
npm ERR! peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/apollo
npm ERR! @nestjs/apollo@"12.0.11" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/graphql
npm ERR! @nestjs/graphql@"12.0.11" from the root project
npm ERR! peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/apollo
npm ERR! @nestjs/apollo@"12.0.11" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-18T08_52_04_432Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-18T08_52_04_432Z-debug-0.log
Pull Request Test Coverage Report for Build 6bd09931-b168-4df2-9bfd-aa51c51d4f1d
Details
- 0 of 0 changed or added relevant lines in 0 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage remained the same at 92.18%
| Totals | |
|---|---|
| Change from base Build 1e0356a2-e22d-4b55-94de-8e14e827e7c7: | 0.0% |
| Covered Lines: | 6731 |
| Relevant Lines: | 7302 |