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
{{ message }}
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
According to this thread, we should either be attaching babel-polyfill to global and checking the global before import, or we should be using idempotent-babel-polyfill. Can someone fix this, asap?
Fixed in PR #600
It turns out that @babel/polyfill was being included by @babel/cli, which the project was not using, so I just removed that dependency, which removed the @babel/polyfill dep. This is by far the preferred solution, given ~"libraries shouldn't be changing global state" babel/babel#4019 (comment)
Thanks to @or2008 !!
The codesandbox.io you setup was super useful in quickly reproducing the issue and testing a couple things.
Version of EOSJS
20.0.0-beta2
Describe the bug
When a project that already use babel-polyfill, include this library, an exception occur:
Uncaught Error: only one instance of babel-polyfill is allowed
To Reproduce
check here the code to reproduce:
https://codesandbox.io/s/q33k7vmk14
as far as I know, 3rd party libraries, such this one, should not include babel-polyfill, check the answer here for more info:
https://stackoverflow.com/questions/34962902/should-javascript-library-which-uses-es6-and-es7-features-require-babel-polyfill
The text was updated successfully, but these errors were encountered: