@angular-devkit/build-angular update from 12.1.x to 12.2.x SSR fails to serve
See original GitHub issue🐞 Bug report
Command (mark with an x
)
- new
- build
- serve
- test
- e2e
- generate
- add
- update
- lint
- extract-i18n
- run
- config
- help
- version
- doc
Is this a regression?
Yes, the previous version in which this bug was not present was: 12.1.4
Description
When building a SSR application, and serving the SSR application, it used to work, but after the update, an error is logged during the process.
TypeError: Cannot convert undefined or null to object
at Function.getPrototypeOf (<anonymous>)
at /Users/Sources/angular-starterkit/dist/server/main.js:1:2701809
at Object.66252 (/Users/Sources/angular-starterkit/dist/server/main.js:1:2815455)
at __webpack_require__ (/Users/Sources/angular-starterkit/dist/server/main.js:1:3657752)
at Object.42853 (/Users/Sources/angular-starterkit/dist/server/main.js:1:2904269)
at __webpack_require__ (/Users/Sources/angular-starterkit/dist/server/main.js:1:3657752)
at Module.25944 (/Users/Sources/angular-starterkit/dist/server/main.js:1:2908930)
at __webpack_require__ (/Users/Sources/angular-starterkit/dist/server/main.js:1:3657752)
at app (/Users/Sources/angular-starterkit/dist/server/main.js:1:5131921)
at run (/Users/Sources/angular-starterkit/dist/server/main.js:1:5133175)
🔬 Minimal Reproduction
https://github.com/rickvandermey/angular-starterkit/tree/feature/update-deps
Steps:
npm ci
npm run start:ssr
🌍 Your Environment
_ _ ____ _ ___
/ \ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__| | | | | | |
/ ___ \| | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ \_\_| |_|\__, |\__,_|_|\__,_|_| \____|_____|___|
|___/
Angular CLI: 12.2.5
Node: 14.16.1
Package Manager: npm 7.21.0
OS: darwin x64
Angular: 12.2.5
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router, service-worker
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1202.5
@angular-devkit/build-angular 12.2.5
@angular-devkit/core 12.2.5
@angular-devkit/schematics 12.2.5
@nguniversal/express-engine 12.1.0
@schematics/angular 12.2.5
rxjs 7.3.0
typescript 4.3.5
webpack 5.52.0
Issue Analytics
- State:
- Created 2 years ago
- Comments:7
Top Results From Across the Web
npm - @angular-devkit/build-angular dependency issue while ...
Upon running ng update @angular/cli@12 I get the below error: npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm...
Read more >@angular-devkit/build-angular - npm
This package contains Architect builders used to build and test Angular applications and libraries. Builders. Name, Description. app-shell ...
Read more >Upgrading Angular application from older version to 12 version
Project managers have to spare some sprints in upgrading Angular applications apart from regular development and functional user stories.
Read more >Angular CLI 13.0.0-next.0 Release - GitClear
Build warnings after migrating to Angular 12.0.0 for external .css files `Unable to locate stylesheet` · #20794. [12.2.x] Update Angular peer dependencies ...
Read more >ng update - Angular
Whether to allow updating when the repository contains modified or untracked files. boolean, false. --create-commits. Create source control commits for updates ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@krzkz94, it looks like the commit was not cherry-picked due to a conflict.
We should be addressing this in the next patch release.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.