Bump webpack and @angular-devkit/build-angular in /frontend#12
Bump webpack and @angular-devkit/build-angular in /frontend#12dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [webpack](https://github.com/webpack/webpack) to 5.105.0 and updates ancestor dependency [@angular-devkit/build-angular](https://github.com/angular/angular-cli). These dependencies need to be updated together. Updates `webpack` from 5.94.0 to 5.105.0 - [Release notes](https://github.com/webpack/webpack/releases) - [Changelog](https://github.com/webpack/webpack/blob/main/CHANGELOG.md) - [Commits](webpack/webpack@v5.94.0...v5.105.0) Updates `@angular-devkit/build-angular` from 17.3.17 to 21.1.3 - [Release notes](https://github.com/angular/angular-cli/releases) - [Changelog](https://github.com/angular/angular-cli/blob/main/CHANGELOG.md) - [Commits](angular/angular-cli@17.3.17...v21.1.3) --- updated-dependencies: - dependency-name: webpack dependency-version: 5.105.0 dependency-type: indirect - dependency-name: "@angular-devkit/build-angular" dependency-version: 21.1.3 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
javascript
Walkthrough
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
| }, | ||
| "devDependencies": { | ||
| "@angular-devkit/build-angular": "^17.3.2", | ||
| "@angular-devkit/build-angular": "^21.1.3", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@angular-devkit/build-angular 21.1.3 angular version compatibility requirements
💡 Result:
@angular-devkit/build-angular@21.1.3 is intended for Angular v21 projects. Its key compatibility requirements (from its peerDependencies / engines) are:
- Angular framework packages:
@angular/core,@angular/compiler-cli,@angular/localize,@angular/platform-browser,@angular/platform-server,@angular/service-workerall^21.0.0(andng-packagr^21.0.0) [1] - SSR (if used):
@angular/ssr^21.1.3[1] - TypeScript:
>=5.9 <6.0[1] - Node.js (engine):
^20.19.0 || ^22.12.0 || >=24.0.0[1] (matches Angular 21’s published platform support table [2])
Practical guidance: keep @angular-devkit/build-angular on the same major (and typically same minor/patch) as @angular/cli and your Angular 21 packages to avoid peer-dependency conflicts.
Sources: [1] https://app.unpkg.com/%40angular-devkit/build-angular%4021.1.3/files/package.json, [2] https://angular.dev/reference/versions
🌐 Web query:
Angular 21 @angular-devkit/build-angular version requirements matrix
💡 Result:
Angular 21 ↔ @angular-devkit/build-angular version matrix
Rule of thumb: keep these in lockstep (same major/minor; ideally same patch): @angular/* 21.x, @angular/cli 21.x, @angular-devkit/build-angular 21.x. Angular’s official compatibility table is published per Angular version line (21.0.x, 21.1.x, etc.).[1]
| Angular framework line | Use @angular-devkit/build-angular |
Runtime / tooling requirements (from Angular 21 compatibility) |
|---|---|---|
| 21.0.x | 21.0.x | Node.js: `^20.19.0 |
| 21.1.x | 21.1.x | Same compatibility line as Angular 21 (unless Angular updates the table for 21.1.x specifically).[1] |
| 21.2.x | 21.2.x | Same note as above.[1] |
Also commonly required in Angular 21 projects: zone.js ~0.15.0 (peer dep of @angular/core@21.0.0).[2]
Release timing context: Angular CLI 21.0.0 released Nov 19, 2025, and its release notes indicate TypeScript versions older than 5.9 are not supported (tooling expectation aligned with the Angular 21 compatibility table).[3]
Sources: [1] Angular “Version compatibility” table, [2] @angular/core@21.0.0 package metadata, [3] Angular CLI 21.0.0 release notes.
🌐 Web query:
angular-devkit build-angular 21.x angular 17.x compatibility
💡 Result:
@angular-devkit/build-angular must match your Angular/CLI major version.
@angular-devkit/build-angular@21.xdeclares peer deps on Angular 21 packages (e.g.@angular/core,@angular/compiler-cli, etc. all^21.0.0). So it is not compatible with Angular 17.x. [1]- For Angular 17.x, you should use
@angular-devkit/build-angular@17.x, which peers on@angular/compiler-cli(and related Angular packages)^17.0.0. [2]
If you’re staying on Angular 17, keep @angular/cli and @angular-devkit/build-angular on 17.x. If you upgrade to build-angular 21.x, you should upgrade the project to Angular 21 as well (and follow its required Node/TypeScript ranges). [1][3]
Sources:
[1] @angular-devkit/build-angular@21.0.4 package.json (peerDependencies) — UNPKG
[2] @angular-devkit/build-angular@17.1.0 package.json (peerDependencies) — UNPKG
[3] Angular versions reference — angular.dev
Critical: Major version mismatch—build will fail
@angular-devkit/build-angular@21.1.3 requires:
- Angular packages
@angular/core,@angular/compiler-cli, etc. all^21.0.0 - TypeScript
>=5.9 <6.0
Current package.json has:
- Angular packages at v17.x
- TypeScript at ~5.3.3 (too old)
Fix: Either downgrade @angular-devkit/build-angular to 17.x, or upgrade all Angular packages + TypeScript to v21.
Bumps webpack to 5.105.0 and updates ancestor dependency @angular-devkit/build-angular. These dependencies need to be updated together.
Updates
webpackfrom 5.94.0 to 5.105.0Release notes
Sourced from webpack's releases.
... (truncated)
Changelog
Sourced from webpack's changelog.
... (truncated)
Commits
1486f9achore(release): new release1a517f6feat: added thetsconfigoption for theresolveroptions (#20400)7b3b0f7feat: supportimport.defer()for context modulesc4a6a92refactor: more types and increase types coverage5ecc58dfeat: consider asset module as side-effect-free (#20352)cce0f69test: avoid comma operator in BinaryMiddleware test (#20398)cd4793dfeat: support import specifier guard (#20320)fe48655docs: update examples (#20397)de107f8fix(VirtualUrlPlugin): set resourceData.context to avoid invalid fallback (#2...a656ab1test: add self-import test case for dynamic import (#20389)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for webpack since your current version.
Updates
@angular-devkit/build-angularfrom 17.3.17 to 21.1.3Release notes
Sourced from
@angular-devkit/build-angular's releases.... (truncated)
Changelog
Sourced from
@angular-devkit/build-angular's changelog.... (truncated)
Commits
0a8860drelease: cut the v21.1.3 releasee80d7c5build: update dependency@modelcontextprotocol/sdkto v1.26.0f6cc58cbuild: update webpack dependency to version 5.105.0133cf28build: update cross-repo angular dependencies to v21.1.3ed0b4c5build: update rules_browsers digest to e08ae3331931f6build: update github/codeql-action action to v4.32.194a830cbuild: update dependency@modelcontextprotocol/sdkto v1.25.37a2ec50build: update cross-repo angular dependenciesd5a8314build: configure Jasmine to allow duplicate describe block namesf4c14f0build: lock file maintenanceDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.