Release v4.2.3 depends on @babel/runtime == 7.0.0-beta.53 #264
Comments
|
I see this was the solution for a hotfix babel/runtime dropping core-js... maybe this shouldn't use the runtime transform at all and instead use rollup and keep the used runtime functions deduped at the top of the bundle. (#243) Our build was fixed by pinning to 4.1.1. |
josephfrazier
added a commit
to josephfrazier/xregexp
that referenced
this issue
Jan 8, 2019
Fixes slevithan#264 See slevithan#262 (comment) See here for more info on the `@babel/plugin-transform-runtime` change: https://babeljs.io/docs/en/next/babel-plugin-transform-runtime#corejs
slevithan
pushed a commit
that referenced
this issue
Jan 8, 2019
Fixes #264 See #262 (comment) See here for more info on the `@babel/plugin-transform-runtime` change: https://babeljs.io/docs/en/next/babel-plugin-transform-runtime#corejs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The recent release seems to have a stale hard dependency on @babel/runtime. (no range)
As a quick fix, (until this project is updated to use the final release of babel 7), you could drop the runtime?
The text was updated successfully, but these errors were encountered: