Skip to content

Commit 9e369c7

Browse files
fix(core): drop the unused optional @angular/platform-server peer (#3792)
npm 10, and npm 11 before 11.20, resolve a missing optional peer anyway while installing. For an app whose package.json uses caret ranges and whose Angular is one patch behind the newest, npm picks the newest @angular/platform-server, which requires that exact newest @angular/core, and the install stops with ERESOLVE. Every current Node line bundles one of those npm versions. Nothing in the published package imports @angular/platform-server, so the peer is removed. Apps that render on the server still install it themselves, as they already do. (cherry picked from commit bbce8f0)
1 parent 03a7017 commit 9e369c7

1 file changed

Lines changed: 1 addition & 3 deletions

File tree

‎src/package.json‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,13 +30,11 @@
3030
"@angular/common": "^20.0.0",
3131
"@angular/core": "^20.0.0",
3232
"@angular/platform-browser": "^20.0.0",
33-
"@angular/platform-server": "^20.0.0",
3433
"rxjs": "~7.8.0",
3534
"firebase-tools": "^14.0.0 || ^15.0.0"
3635
},
3736
"peerDependenciesMeta": {
38-
"firebase-tools": { "optional": true },
39-
"@angular/platform-server": { "optional": true }
37+
"firebase-tools": { "optional": true }
4038
},
4139
"dependencies": {
4240
"firebase": "^11.8.0",

0 commit comments

Comments
 (0)