Comments (14)
Reinstall babel-loader
. rm -rf node_modules && npm install
to get the latest version of babel
.
from babel-loader.
Fix my problema installing "@babel/runtime": "7.0.0-beta.55",
from babel-loader.
@rifler @babel/plugin-transform-runtime
is a plugin for inserting imports that reference @babel/runtime
. This means that @babel/runtime
is required by the actual published code, and you should have @babel/runtime
in dependencies
, whereas you'd have @babel/plugin-transform-runtime
in devDependencies
.
Your code may have broken if you published your lib with the @babel/runtime
dependency with ^
in the version number however, since that means you are stating that you depend on any future version of the @babel/runtime
, and since we are still in a beta version, that can be a dangerous thing to do because things are still unstable. You want to be sure that the transform plugin, and @babel/runtime
, have exactly the same version.
from babel-loader.
I am encountering this same issue and I have tried deleting node_modules and re-installing several times as well as npm clean cache --force and doing the same thing over. I always get this error in the browser when I run my .net core app: Error: Module build failed: Error: Cannot find module '@babel/helpers'
from babel-loader.
@grawk It's an internal babel
"issue" unrelated to babel-loader
. The internal structure of babel-runtime
was changed which means that older babel
versions output incorrect references to babel-runtime
.
from babel-loader.
In lib all @babel/*
packages are in devDeps (beta.54), and consumer decides to use rc-1 version. After update all packages in lib to rc-1 (still all of them in devDeps) things start to work, because webpack now is able to find @babel/runtime/helpers/builtin/es6/objectWithoutProperties
Thank you for response, I'll move @babel/runtime
to dependencies
, because one day I may want to enable ssr
from babel-loader.
thank you!
from babel-loader.
This didn't work for me. Should I see a patch version bump?
from babel-loader.
OK. New to babel so pardon ignorance. I ran across this issue with https://github.com/krakenjs/confit which had "babel": "^4.6.6" as a devDependency and "babel-runtime": "^4.6.6" as a dependency. When I installed confit into a module where I use it, confit installed 4.7.8 of the babel-runtime, and I received the error mentioned in the issue title. I currently have a PR to confit pending which locks the babel versions to 4.7.3, which i tested and know to be working.
from babel-loader.
I'll need to make it much more obvious that the versions need to be locked
in the docs since they're essentially internal APIs.
On Wednesday, 11 March 2015, Matt Edelman [email protected] wrote:
OK. New to babel so pardon ignorance. I ran across this issue with
https://github.com/krakenjs/confit which had "babel": "^4.6.6" as a
devDependency and "babel-runtime": "^4.6.6" as a dependency. When I
installed confit into a module where I use it, confit installed 4.7.8 of
the babel-runtime, and I received the error mentioned in the issue title. I
currently have a PR to confit pending which locks the babel versions to
4.7.3, which i tested and know to be working.Reply to this email directly or view it on GitHub
#39 (comment).
Sebastian McKenzie
from babel-loader.
Maybe my mind was playing tricks but I appeared to have the same version of both modules (4.7.8) when I encountered the problem. Are you saying that I encountered it because the versions didn't match at some point?
from babel-loader.
Most likely. npm is really weird most of the time. babel-runtime is built
and published the same whenever I publish a new babel version so they're
guaranteed to be compatible.
On Wednesday, 11 March 2015, Matt Edelman [email protected] wrote:
Maybe my mind was playing tricks but I appeared to have the same version
of both modules (4.7.8) when I encountered the problem. Are you saying that
I encountered it because the versions were off at some point?Reply to this email directly or view it on GitHub
#39 (comment).
Sebastian McKenzie
from babel-loader.
Have you tried updating the @bable/runtime package
from babel-loader.
I publish lib with import _objectWithoutProperties from "@babel/runtime/helpers/builtin/es6/objectWithoutProperties";
. Before publish, this lib runs @babel/...
version beta.54
.
Consumer, for example, uses rc.1
, and this code breaks.
What is the right way to publish libs? move @babel
from devDeps to deps?
from babel-loader.
Related Issues (20)
- [Bug]: TypeError: this.getOptions is not a function + SPFx HOT 8
- @babel/plugin-transform-optional-chaining, configuration does not take effect HOT 1
- BunnyJs
- `module.exports` is returned instead of `module.exports.default` when importing from node_modules HOT 1
- Plugin transform-runtime generates incorrect commonjs wrapper HOT 2
- Issue while creating build for React JS Application HOT 6
- unknow option .default HOT 5
- Adding ES6 `import("find-cache-dir");` should be a breaking change. HOT 7
- You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders | HOT 1
- [Bug]: HOT 2
- Cache files take up too much disk space
- Refresh time is too slow in expo react-native project after upgrade HOT 14
- Babel-loader Cache - unable to cache in changing directory environment HOT 2
- After upgrade my nodejs version 16.8.0 to 16.9.0, I am getting this error "You may need an additional loader to handle the result of these loaders" HOT 1
- Bug Error Run npm ci npm ERR! Cannot read property '@babel/cli' of undefined npm ERR! HOT 1
- Feature request: Different browserslistEnv based on webpack target. HOT 1
- You may need additional loaders
- semver vulnerable to Regular Expression Denial of Service HOT 3
- Bump semver dependency to >= 7.5.2 HOT 1
- Vulnerable dependencies (indirect security issues) HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from babel-loader.