Skip to content
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

Version compatibility issues #760

Open
c0deCn opened this issue May 9, 2023 · 3 comments
Open

Version compatibility issues #760

c0deCn opened this issue May 9, 2023 · 3 comments

Comments

@c0deCn
Copy link

c0deCn commented May 9, 2023

I'm currently using vue 2 + webpack 4 (a rather outdated configuration)

Now I have a problem: when "browserslist": [ "> 1%", "last 2 versions" ], an error occurs when a package is introduced

When set to

"browserslist": [ "defaults and supports es6-module", "maintained node versions" ].

When the error is fixed, the error is resolved, but the callback for async.queue mapLimit etc. is gone. Please ask the gods how to achieve a compatible solution

@ai
Copy link
Member

ai commented May 9, 2023

What error do you have exactly?

@c0deCn
Copy link
Author

c0deCn commented May 9, 2023

if browserslist": [ "> 1%", "last 2 versions" ], the
The error is:
TypeError: Cannot convert a BigInt value to a number
at Math.pow ()
at SWUFpSqrtRatio (weierstrass.ts:1097:1)
at mapToCurveSimpleSWU (weierstrass.ts:1166:1)
at eval (secp256k1.ts:249:1)
at ./node_modules/_@noble_curves@1.0.0@@noble/curves/secp256k1.js (chunk-vendors.js:15341:1)
at webpack_require (app.js:854:30)
When set to "browserslist": [ "defaults and supports es6-module", "maintained node versions" ]. The error is resolved, but the callbank functions for methods such as async.queue mapLimit are gone on our system, and we are currently looking for a compatible solution that will allow us to get our system running without massive changes

@ai
Copy link
Member

ai commented May 9, 2023

The stacktrace came not from Browserslist. Seems like it is a bundler or webapp issue. Browserslist config changes just enable some polyfill which broke or fix thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants