exceljs 3.0.1 and Angular 8 installation issue
See original GitHub issueI love exceljs and with version 2 it was no problem to get it to work with Angular. But after the upgrade to the new major release 3 I can’t get it to work anymore. The compilation works fine, but it breaks on starting the application with:
Error: Zone.js has detected that ZoneAwarePromise `(window|global).Promise` has been overwritten.
Most likely cause is that a Promise polyfill has been loaded after Zone.js (Polyfilling Promise api is not necessary when zone.js is loaded. If you must load one, do so before loading zone.js.)
Does anybody has an idea or solution how this can be fixed so that it runs smoothly again?
Thx and regards, Lars
Issue Analytics
- State:
- Created 4 years ago
- Reactions:14
- Comments:26 (7 by maintainers)
Top Results From Across the Web
exceljs 3.0.1 and Angular 8 installation issue - Bountysource
I love exceljs and with version 2 it was no problem to get it to work with Angular. But after the upgrade to...
Read more >exceljs - npm
Read, manipulate and write spreadsheet data and styles to XLSX and JSON. Reverse engineered from Excel spreadsheet files as a project.
Read more >Exceljs Angular 7 - StackBlitz
Starter project for Angular apps that exports to the Angular CLI.
Read more >angularjs - Angular upgrade from 9 to 10 getting error "export ...
I Tried to upgrade my application from angular 9 to 10 but migration got failed by giving an error "unable to move esnext...
Read more >Exporting a grid to Excel using ExcelJs is not working for ...
I'm using ExcelJs 4.0.1. Also using Angular 8. Below is my onExporting() code. If I take out the pageSetup options then the resulting ......
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
The error still exists with the latest release of ExcelJS 3.5 and all suggested solutions are not feasible. Is there any working solution/fix on the horizon?
not really! The problem is a new one. As written in the original posting: exceljs v2.0.1 is working properly. The problem occurs since exceljs v3 (current 3.1.0).