Consider using BigInt constructor for compatibility.

[anicolao]

No description provided.

[rokicki]

This does enhance the ability to find BitInt stuff in the code. I'm pretty sure typescript "does the right thing" here with respect to literals but even if it doesn't, it's not going to affect performance.

[lgarron]

Thanks! I'm glad this is such a simple fix.

I will maintain that projects like Vite are broken if they break big int code, given that it's been available in all environments for 2 years: https://caniuse.com/?search=bigint (See vitejs/vite#9062 for more context, where it seems that their lack of big int compat is accidental, not on purpose.)
For that reason, I'm generally against workarounds like this in our codebase. But I think this one is definitely worth it, thanks for looking into it!

[lgarron]

Published as part of v0.29.1! 😄
https://github.com/cubing/cubing.js/releases/tag/v0.29.1

[anicolao]

Even after reading that thread I don't understand why there are two different environments to configure for vite - the optimizeDeps vs the build ... but in any event I'm glad to have the workaround in 0.29.1! Thanks.