You can import the default export by either import Test2 from ‘./test’; or import {default as Test2} from ‘./test’; The default export doesn’t have Test as a name that you would need to alias – you just need to import the default under the name that you want. The best docs I’ve found so far … Read more
With UglifyJsPlugin we can handle comments, warnings, console logs but it will not be a good idea to remove all these in development mode. First check whether you are running webpack for prod env or dev env, if it is prod env then you can remove all these, like this: var debug = process.env.NODE_ENV !== … Read more
This is an issue with Javascript source maps, which don’t currently support mapping symbol names, and babel, which changes the names of import-ed modules when compiling to CommonJS from ES2105 module syntax. Babel does this to fully support the fact that ES2015 modules export bindings by resolving all references to imports whenever they are used … Read more
From the docs https://babeljs.io/docs/en/config-files#project-wide-configuration Babel has two parallel config file formats which can be used together, or independently. Project-wide configuration babel.config.json files, with the different extensions File-relative configuration .babelrc.json files, with the different extensions package.json files with a “babel” key Babel loads .babelrc.json files, or an equivalent one using the supported extensions, by searching up … Read more
I’m going to start this answer saying that I have never used Flow, so I can’t say much about it. But, we are using React and TypeScript at work and it works great. We have all the benefits I imagine you already know about, like refactoring, type safety, autocompletion, etc. Sure, for what I have … Read more
Based on the documentation, you should be able to write .babelrc { “ignore”: [ “**/*.test.js” ] } However, I was able to verify that this does not seem to work. I tried it with version 6.5.1 (babel-core 6.5.2). At the same time, the following does work: babel src –out-dir build –ignore ‘**/*.test.js’ That is the … Read more
Basically speaking, they serve different purposes and usually show up together. I will explain what they are designed to do. babel Babel is a transpiler. It can translate all kinds of high version ECMAScript ( not only ECMAScript, but it’s easy to understand) into ES5, which is more widely supported by browsers (especially older versions). … Read more
The easiest way would be to change main: ‘./resources/assets/js/main.js’, services: ‘./resources/assets/js/services.js’ to be main: [‘babel-polyfill’, ‘./resources/assets/js/main.js’], services: [‘./resources/assets/js/services.js’] so that the polyfill is loaded and executed as part of each entry point without your files needing to know about it. This assumes that both main and services are loaded on the same page. If they … Read more
You don’t tell Babel to target ES5, you choose the necessary presets/plugins that do that for you. For example, if you use the es2015 preset, this will compile ES6 code to ES5-compatible code. You don’t specify a “target”. The guide below will take you through using Babel to transform ES6 code into code that can … Read more
That syntax is an experimental proposed syntax for the future, it is not part of es2015 or react so you’ll need to enable it. npm install –save-dev babel-plugin-transform-object-rest-spread and add “plugins”: [“transform-object-rest-spread”] into .babelrc alongside your existing presets. Alternatively: npm install –save-dev babel-preset-stage-3 and use stage-3 in your presets to enable all stage-3 experimental functionality.