You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Its due to ESM, fully qualified names are required in our lib code and we can hint node for that using --experimental-specifier-resolution=node#5904 (comment) , but in case of CRA its not considering this flag.
Now we stopped running into esm issues, its back being polyfill errors like in 1.x, i think we could get rid of the polyfills after the release and work on that. not sure how hard that would be, i think marin said it might take some work.
I dont think forcing cjs will work since its a polyfill issue, I think if people want to use web3js in CRA or angular we can provide them a cdn min.js build. thoughts?
Is there an existing issue for this?
Current Behavior
running into a build error with CRA. browser build issue that needs to be investigated
Expected Behavior
Should work fine
Steps to Reproduce
create CRA project with 4.x
Web3.js Version
4
Environment
Anything Else?
No response
The text was updated successfully, but these errors were encountered: