babel против babel-core против babel-loader против babel-preset-2015 против babel-preset-react vs babel-polyfill

Я настраивал Webpack для своего проекта React и запутался между babel, babel-core babel-loader babel-preset-2015, babel-preset-2015 и babel-preset-react. Я знаю, что Babel необходим для преобразования кода ES7 или ES6 в ES5, но в моем package.json я установил все эти зависимости, кроме Babel, и они также как devDependencies.

Может кто-нибудь объяснить, в чем разница между всем этим и почему все они необходимы для моего проекта? Нет ли какой-то одной зависимости, чтобы заменить их всех? И если они так важны, почему они включены как devDependencies?

Ответ 1

галдеж

Babel doesn't do anything,It basically acts like const babel = code => code; 
by parsing the code and then generating the same code back out again.

You will need to add some plugins for Babel to do anything like transpiling es6,JSX.

столпотворение-жильный

if you want to use babel in your real project, you need to install babel but 
there no babel package available.

   babel split it up into two separate packages: babel-cli and babel-core

   **babel-cli** : which can be used to compile files from the command line.

   **babel-core** : if you want to use the Node API you can install babel-
      core, Same as "babel-cli" except you would use it programmatically inside your app.

   use "babel-cli" or "babel-core" to compile your files before production.

перед тем как двигаться дальше,

preset vs plugin:

We can add features(es6,JSX) one at a time with babel plugins(es2015), 
    or 
we can use babel presets to include all the features(es6) of a particular year.

Presets make setup easier.

столпотворение-предустановленные es2015

babel-preset-env supports es2015 features and replaces es2015, es2016, 
  es2017 and latest.

So use babel-preset-env, it behaves exactly the same as babel-preset-latest 
 (or babel-preset-es2015, babel-preset-es2016, and babel-preset-es2017 together).

Бабель-запрограммированным реагируют

transform JSX into createElement calls like transforming react pure class to 
   function and transform react remove prop-types.

столпотворение-polyfill

Without babel-polyfill, babel only allows you to use features like arrow 
 functions, destructuring, default arguments, and other syntax-specific 
 features introduced in ES6.

The new ES6 built-ins like Set, Map and Promise must be polyfilled

To include the polyfill you need to require it at the top of the entry point 
  to your application.

столпотворение-погрузчик

you done with babel-core, babel-cli, and why need preset, plugins and now 
  you are compiling ES6 to ES5 on a file-by-file basis by babel-cli every time.

to get rid-off this, you need to bundle the task/js file. For that you need 
   Webpack.

Loaders are kind of like "tasks", They gives the ability to leverage 
 webpack bundling capabilities for all kinds of files by converting them 
 to valid modules that webpack can process.

Webpack has great Babel support through babel-loader

devDependencies

When you deploy your app, modules in dependencies need to be installed or 
your app won't work. Modules in devDependencies don't need to be installed 
on the production server since you're not developing on that machine.

These packages are only needed for development and testing.

Разве нет единой зависимости для их замены?

as you read the above states, You need some presets and loaders to transpile 
 es2015 or JSX files.