Stab in the dark, is this function inside a class? Arrow functions that are members of a class are not included in ES2015 (or 2016). If you want to do something like: class Foo { bar = (baz) => { console.log(baz); } } You’ll need to include babel-transform-class-properties. In your example, you’ll need to: npm … Read more
Browserify is meant to be fed a single “entry point” file, through which it recursively traverses all of your require statements, importing the code from other modules. So you should be require‘ing the _babel.js versions of modules, not _browserified.js ones. From the looks of it, you intend for your app’s “entry point” to be demos/helicopter_game/PlayState_browserified.js, … Read more
From babeljs.io/docs/plugins: (as of 9/30/2016) Plugin/Preset Ordering Ordering matters for each visitor in the plugin. This means if two transforms both visit “Program”, the transforms will run in either plugin or preset order. Plugins run before Presets. Plugin ordering is first to last. “plugins”: [ “transform-decorators-legacy”, // will run first “transform-class-properties” // will run second … Read more
I think, this might have to do with this weird hackfix that is being touted in a bunch of places that tells you to place next/babel in your eslint config file for some reason (e.g. here). It probably was a hackfix for an old bug in older next.js versions. But as of (at least) summer … Read more
This is probably happening because you, like me, were using the old babel parser. Package babel-eslint has been deprecated since March of 2020. The package was migrated to new repo, if you want to know more, I recommend you check Babel git. Just change and install or update to the latest parser packaged in .eslintrc.js: … Read more
No, Babel and Webpack is not necessary for React stack. You can still find other alternatives to build your favourite stack such as Browserify and Gulp. However, if you want to make things easier, I do recommend you learn and use Babel and Webpack together with React because: You can use modules. You can use … Read more
One possible way: const result = doSomething(), { a, b } = result; You still have to duplicate the name, though. const token isn’t quite right-handy. )
They are the same. All babel-core/register does is require(‘babel-register’). https://github.com/babel/babel/blob/cb8c4172ef740aa562f0873d602d800c55e80c6d/packages/babel-core/register.js#L3 The recommended usage is babel-register since that is the module where the code actually lives, and babel-core/register has been removed in Babel 7.x. Better to depend specifically on the module you use, rather than load it as a side-effect of babel-core.
If I put presets inside webpack.config I should be able to delete .babelrc or vice verse. No, this is not the case. Specifying the presets in the webpack config will only affect webpack, everything else that uses babel (e.g. babel-node, babel-register, etc.) will not care about your webpack config and therefore doesn’t see them. The … Read more
It is a known issue. If you are using yarn, you can easily get around it using resolutions. Add the following to your package.json to allow yarn to resolve babel-loader version 8.1.0 (the version required by CRA, not Storybook): “resolutions”: { “babel-loader”: “8.1.0” }, After that, make sure to run yarn install to refresh your … Read more