New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Unable to run the application (ng serve) #13
Comments
Hi @perseghini, Thank you for working with our products. We tried updating but we also receive this fatal error. We will still try to fix it and we will come with updates. Thank you, |
Same issue... |
Hi @fb2062, Thank you for working with our products. Can you please tell me what error do you get? Thank you, |
Hi Rares, As summary; Version Operating System Device Browser & Version Steps to reproduce What I get? Fatih. |
Hi @fb2062, Please replace in package.json Please let me know if it works. Thank you, |
Hi Rares, It worked. Fatih. |
Hey @rarestoma, This fixed the issue, |
Can this solution be added to the README? Maybe as a 'Gotcha' suggestion in the event, a user encounters this error? My company bought this theme today and this would have saved us some time if it was included in the README. Thank you for building this theme. |
Version
latest (1.2.0)
Reproduction link
https://jsbin.com/
Operating System
Mac OS 10.15.7
Device
MacBook Pro
Browser & Version
Chrome (latest)
Steps to reproduce
npm install
ng serve
What is expected?
The application should compile and run
What is actually happening?
ERROR in ./node_modules/@angular/common/ivy_ngcc/fesm2015/common.js 4283:12-27
"export 'ɵisSubscribable' was not found in '@angular/core'
Solution
It seems "Argon Dashboard Pro Angular" was not completely migrated to Angular11. Some packages are still using an old incompatible version (ie: @angular/http:7.2.16 ).
You can also try to run "ng update @angular/cli", "ng update @angular/core" and "rxjs" to see some current issues with the migration to Angular 11.
I tried to manually update the old packages but then ran into this issue:
"FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory"
Additional comments
The text was updated successfully, but these errors were encountered: