version mismatch error
See original GitHub issueHi, I am taking this error.
ERROR in Metadata version mismatch for module /home/myuser/Code/crm/node_modules/@toverux/ngx-sweetalert2/toverux-ngx-sweetalert2.d.ts, found version 4, expected 3, resolving symbol CustomerRegisterModule in /home/myuser/Code/crm/src/app/pages/customer-register/customer-register.module.ts, resolving symbol CustomerRegisterModule in /home/myuser/Code/crm/src/app/pages/customer-register/customer-register.module.ts, resolving symbol CustomerRegisterModule in /home/myuser/Code/crm/src/app/pages/customer-register/customer-register.module.ts
What could be reason?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
VALORANT version mismatch error | How to fix ... - Dot Esports
To solve this issue, simply close out of the game and restart the client, which should prompt you to download the latest version....
Read more >This is how to fix the Valorant version mismatch error - WIN.gg
The version mismatch error is simply when a player loads up the game while running an outdated version of the game. Developers very...
Read more >Valorant mismatch: How to fix mismatch error in the game?
The Valorant version mismatch error occurs when players fire up the game without updating it. This might occur whenever a new patch has...
Read more >Fix Valorant Version Mismatch Error After Latest Dec Update
The version mismatch error is generally caused by updates to Valorant when players run a client version that's different from the actual version...
Read more >How to fix Version Mismatch error in Valorant - Sportskeeda
The Version Mismatch error occurs when the installed version of the game does not match the one on the server. Since different versions...
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 Free
Top 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
Yeah, seems pretty clear now. I’ll close this and recommend people to upgrade their Angular version or staying on an old build of ngx-sweetalert2, setting their dependency on
~3.0.1
(I’m really sorry for the unwanted breaking change, I’ll be more careful on that).Yeah, the metadata file (edited). So updating to Angular 5 should solve this issue I assume. Thx.