ERROR in Error: Metadata version mismatch for module about angularx-qrcode

[carrieXin]

maybe you should update "angularx-qrcode": "^1.0.2" to "angularx-qrcode": "1.0.1" in your package.json

[stephen-eas]

same issue. 1.0.3 on angular 4.4.7 found version 4 expected version 3.
Oddly it worked for about a minute. tried the modules clear and reinstall, but this seems to be stuck with that bug/warning

difference between working and not was editing a CSS file.
reverted those changes to no effect, very weird.

Same setup as you, I was able to resolve and successfully build by changing from ^1.0.3 to 1.0.1 in the package.json file

After building and importing the module, you'll need to ensure you're using the correct attributes for the 1.x versions. From the docs below:

# Old code in 1.x
<qrcode [qrdata]="'Your data'" [size]="256" [level]="'M'" usesvg="true"></qrcode>

# New code in 2.x or 10.x
<qrcode [qrdata]="'Your data'" [width]="256" [errorCorrectionLevel]="'M'" [elementType]="'svg'"></qrcode>

[Cordobo]

Hi johns24,

this might be fixed by completely removing your node_modules folder and run npm install again on your project.

[sunnyxujian]

Your @angular/animations is on version 5.x.x and other @angular/ packages are on 4.x.x. All @angular/* packages must be aligned, i.e. have the exact same version number for the app to be able to compile.
your project is 4.x.x , you must install below 1.0.0 version of this weight

[Cordobo]

@Itherma I'm a little bit confused by your comment, I neither see where @johns24 is on 5.x.x in his package.json nor where angularx-qrcode is probably on a worng version. could you please clarify and go into more detail?

[Cordobo]

Closed for now, please reopen if the issue persists.

[jameskleeh]

yarn.txt

@Cordobo I'm running into this right now with version 1.0.3. I've attached my yarn lock file

[jacksodj]

same issue. 1.0.3 on angular 4.4.7 found version 4 expected version 3.
Oddly it worked for about a minute. tried the modules clear and reinstall, but this seems to be stuck with that bug/warning

difference between working and not was editing a CSS file.
reverted those changes to no effect, very weird.

[jacksodj]

looks like re-running this line fixes it for some period of time:
npm install [email protected] --save

[jacksodj]

ok, a little more detail, running npm start will throw the error.
but if in a different window I run the npm install [email protected] --save
the watcher in the first window will trigger and then recompile correctly.

Note: I also tried the change from ^1.0.3 to 1.0.3 in the package.json file

[utsav-gupta]

@Cordobo Why is this issue closed, has it been fixed?

[Cordobo]

@utsav-gupta it was closed because it couldn't be reproduced by me and the original author did not a provide a repo where I could reproduce it.