Angular 13 build issue with 3.2.0
See original GitHub issueMy CI ran into a build issue with the 3.2.0 release while running Angular 13.
./node_modules/angular-resize-event/fesm2015/angular-resize-event.mjs - Error: Module build failed (from ./node_modules/@angular-devkit/build-angular/src/babel/webpack-loader.js):
TypeError: Cannot create property 'message' on string '/home/circleci/setup-test/myproject/node_modules/angular-resize-event/fesm2015/angular-resize-event.mjs: This application depends upon a library published using Angular version 14.0.2, which requires Angular version 14.0.0 or newer to work correctly.
Consider upgrading your application to use a more recent version of Angular.
31 | }
32 | ResizedDirective.ɵfac = i0.ɵɵngDeclareFactory({ minVersion: "12.0.0", version: "14.0.2", ngImport: i0, type: ResizedDirective, deps: [{ token: i0.ElementRef }, { token: i0.NgZone }], target: i0.ɵɵFactoryTarget.Directive });
> 33 | ResizedDirective.ɵdir = i0.ɵɵngDeclareDirective({ minVersion: "14.0.0", version: "14.0.2", type: ResizedDirective, selector: "[resized]", outputs: { resized: "resized" }, ngImport: i0 });
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
34 | i0.ɵɵngDeclareClassMetadata({ minVersion: "12.0.0", version: "14.0.2", ngImport: i0, type: ResizedDirective, decorators: [{
35 | type: Directive,
36 | args: [{'
at run (/home/circleci/setup-test/myproject/node_modules/@babel/core/lib/transformation/index.js:39:15)
at run.next (<anonymous>)
at Function.transform (/home/circleci/setup-test/myproject/node_modules/@babel/core/lib/transform.js:25:41)
at transform.next (<anonymous>)
at step (/home/circleci/setup-test/myproject/node_modules/gensync/index.js:261:32)
at /home/circleci/setup-test/myproject/node_modules/gensync/index.js:273:13
at async.call.result.err.err (/home/circleci/setup-test/myproject/node_modules/gensync/index.js:223:11)
at /home/circleci/setup-test/myproject/node_modules/gensync/index.js:189:28
at /home/circleci/setup-test/myproject/node_modules/@babel/core/lib/gensync-utils/async.js:84:7
at /home/circleci/setup-test/myproject/node_modules/gensync/index.js:113:33
at step (/home/circleci/setup-test/myproject/node_modules/gensync/index.js:287:14)
at /home/circleci/setup-test/myproject/node_modules/gensync/index.js:273:13
at async.call.result.err.err (/home/circleci/setup-test/myproject/node_modules/gensync/index.js:223:11)
Don’t know if that’s intentional or not, since the package.json states only Angular 14, but the release page says support for Angular 12-14
.
I’ll be locking the dependency/version to "angular-resize-event": "~3.1.1"
for now.
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Angular CLI fails after updating to v13 · Issue #22202 - GitHub
I noticed that the @schematics/angular version seems older, it should be 13 I suppose. I can't figure out how to update it thought....
Read more >ERROR in The Angular Compiler requires TypeScript >=3.1.1 ...
ERROR in The Angular Compiler requires TypeScript >=3.1.1 and <3.2.0 but 3.2.1 was found instead. Seems like Typescript updated but the Angular ...
Read more >Changelog - Cypress Documentation
Fixed an issue with Angular Component Testing where urls within SASS/SCSS files were not being correctly resolved which could result in incomplete styling....
Read more >ng build - Angular
Option Description Value Type Default Value
‑‑aot Build using Ahead of Time compilation. boolean true
‑‑base‑href Base url for the application being built. string
‑‑delete‑output‑path Delete...
Read more >npm err eresolve could not resolve angular - You.com
It means you have dependency conflicts. So try running the following options one by one. Remove node_modules and package-lock.json and then run. npm...
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
We had same issue and had to roll back to
~3.1.1
I also had to lock to 3.1.1 to get it to work with Angular 13.