The `@babel/plugin-transform-runtime` is not found
See original GitHub issueWhy we need this? As long as I know it should be used as devDependency, so why when generating production builds we need it?
And should I add it in my preset too? And one side question: does the plugin reads babel.config.js
when found AND you have babelConfig
option set? My assumption is it’s not? Just for verification.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Cannot find module '@babel/plugin-transform-runtime' from
I m getting the error " Cannot find module '@babel/plugin-transform-runtime' from ...". I have tried every solution on the internet but ...
Read more >"Error: Cannot find module 'babel-plugin-transform-runtime ...
Hello, I had the same issue! I just deleted my node_modules folder, and the package-lock.json, then run npm install, and it solved my...
Read more >babel/plugin-transform-runtime
A plugin that enables the re-use of Babel's injected helper code to save on codesize.
Read more >@babel/plugin-transform-runtime - npm
@babel/plugin-transform-runtime. Externalise references to helpers and builtins, automatically polyfilling your code without polluting globals.
Read more >babel-plugin-transform-runtime - npm package - Snyk
The npm package babel-plugin-transform-runtime was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@babel/plugin-transform-runtime
is added to and merged with the users provided Babel config if it doesn’t already include it. The only reason why it is added is to move shared Babel helpers into import statements rather than duplicating them inline such that they can be shared across chunks without duplication.The reason why you may get the error in the issue title is if you depend on another library that depends strictly on a different version of
@babel/plugin-transform-runtime
(such astsdx
does).As for the side-question: If you override the
babelConfig
option, yourbabel.config.js
file won’t be resolved, so your assumption is correct 😊It’s not example repo. And the thing is long gone. 😉
I couldn’t find the changes I did for that specific issue i linked. So anyway.