-
Notifications
You must be signed in to change notification settings - Fork 62
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
Angular 16 NgxQRCodeModule is not compatible with Angular Ivy #103
Comments
having same issue, any updates on a fix? thank you. |
Don't get your hopes to high that the library will be updated. I just switched to angular2-qrcode. Super easy migration. https://www.positronx.io/angular-generate-or-create-qr-code-using-angular2-qrcode-package/ |
Same issues here! The same happens for the package you suggested @mw108 😢 |
Are you sure? The alternative package ( https://stackblitz.com/edit/stackblitz-starters-coxmss?file=src%2Fmain.ts |
Hi, changing tsconfig.json compilerOptions works for me on angular V15: "target":"es2022", "module":"esnext" and "lib": ["es2022", "dom"] |
This library works in Angular 15, but it doesn't work on Angular 16. |
It does: https://stackblitz.com/edit/stackblitz-starters-coxmss?file=src%2Fmain.ts |
The library
Were you able to make it work? If yes, how? |
Ok, nevermind. I assumed you meant the angular2-qrcode library. Check my answer above: #103 (comment) |
Weird, when I try to import
Does it mean that Besides, they have the Ivy support issue, too. Update: moving
but in browser (DOM) it's
Update 2: using angularx-qrcode instead seems to be working. |
just take these files in the repo -> projects/ngx-qrcode/src/lib -> and make your own component. one less npm package to then worry about |
I'm submitting a...
Current behavior
the library (@techiediaries/ngx-qrcode) which declares NgxQRCodeModule is not compatible with Angular Ivy. Check if a newer version of the library is available
Expected behavior
NgxQRCodeModule is compatible with Angular Ivy
Minimal reproduction of the problem with instructions
Just build a project with angular 16 and above
What is the motivation / use case for changing the behavior?
Error during building
Environment
The text was updated successfully, but these errors were encountered: