What is meant by `Webpack 2 natively understands ES6`?

Question

I have often heard that Webpack 2 (unlike Webpack 1.x ), natively understands ES6 . What does this mean and what follows from this?

Naturally, after receiving answers to this question, the next question will arise about how to change the settings of Babel. At the moment I am using a webpack 2x with the following settings:

package.json

  // ... "babel": { "presets": [ "es2015" ] }, "devDependencies": { "babel-core": "6.22.0", "babel-loader": "6.2.10", "babel-preset-es2015": "6.22.0", // ... "webpack": "^2.4.1" }

webpack.config.js

 // ... module: { rules: [ { test: [ /\.jsx?$/ ], exclude: /node_modules/, use: [ 'babel-loader' ] } ] }, // ...

Which of the above settings is no longer necessary thanks to the so-called "native understanding" of the ES6 Webpack tool?

unless where you heard it was not told more specifically in what an essence?
For example, I will quote words from the famous webpack screencast : "The next version of the Webpack will understand ES6 natively, and the current version works through Babel" (and further presentation deviates from the next version of Webpack).
The screencast is wonderful, but I didn’t understand from this phrase what exactly now it became not necessary to register in the Webpack settings.
es2015 specifically: The es2015 babel preset transforms ES6 Modules to CommonJS by default.

What is meant by `Webpack 2 natively understands ES6`?

0

More articles: