cant use this library in [email protected]

[galmalka21]

are you going to update the library soon to be able to run in [email protected]?

[Rehankhalil462]

@galmalka21 use --legacy-peer-deps flag while installing this package. It will work with [email protected].

[dcastillogi]

For those who are attempting to deploy to Vercel, keep in mind the following steps: Go to Settings > General > Build & Development Settings. Then, override the Install Command by using either npm install --force or npm install --legacy-peer-deps.

[val-samonte]

Big issue tbh. If someone created a fork to fix this please drop it here. Thanks.

[vbsh123]

If this is still relevant, there's a similiar version that works (idk if its forked from this one though but it is based on this)
https://github.com/kybarg/react-qr-scanner

[vairaselvam]

Even I need a solution. I migrated ReactJs from 16 to 18. Now react-qr-reader is throwing error.

[kelvinCJJ]

Any solutions?

[hholmes6]

same

[phanthaiduong22]

I have same issue

[Jcoloma13]

"overrides": {
"react-qr-reader": {
"react": "$react",
"react-dom": "$react-dom"
}
}

You can try this.

[adlarionov]

Just run npm i --legacy-peer-deps react-qr-reader, then in your generated package-lock.json rewrite peerDependencies in node_mobules/react-qr-reader field. Lastly, run npm i. Everything should work.

[h0jeZvgoxFepBQ2C]

Just run npm i --legacy-peer-deps react-qr-reader, then in your generated package-lock.json rewrite peerDependencies in node_mobules/react-qr-reader field. Lastly, run npm i. Everything should work.

I'm not sure if i'm totally right, but just ignoring dependency issues is not the best way forward. this issue should be fixed

[adlarionov]

Just run npm i --legacy-peer-deps react-qr-reader, then in your generated package-lock.json rewrite peerDependencies in node_mobules/react-qr-reader field. Lastly, run npm i. Everything should work.

I'm not sure if i'm totally right, but just ignoring dependency issues is not the best way forward. this issue should be fixed

Yes, you are absolutly right. I just showed my solution to this problem. It is an issue that should be fixed for sure

[mh-jsx]

if you have react > 17 Use this instead
https://www.npmjs.com/package/react-zxing

Both the libraries are using @zxing/library under the hood.