Add forceAllTransforms option and deprecate Uglify target

[existentialism]

Fixes #234.

Added as a deprecation, but can straight remove if we want?

Also, still unsure about the name (useTargetSyntax?)?

[yavorsky]

👍

Also not sure about useSyntax naming. useTargetSyntax maybe can be confusing (we need to specifify targetSyntax or targets are syntax targets) 🙃.

Maybe focus on the code transformation? useTransformations/useTransform?

Or combine all the thoughts and useuseSyntaxTransform?

[existentialism]

@yavorsky thoughts on forceAllTransforms?

With a .babelrc.js you would have:

module.exports = {
  presets: [
    ["env", {
      targets: {
        chrome: 59,
        edge: 13,
        firefox: 50,
      },
      // for uglifyjs...
      forceAllTransforms: process.env === "production"
    }],
  ],
};

[yavorsky]

forceAllTransforms looks better. 👍
But on the other hand, useBuiltIns: "entry" make some transforms also. 🤔

[existentialism]

@yavorsky @hzoo updated the name to forceAllTransforms... can land and rename it later?

[codecov-io]

Codecov Report

Merging #264 into 2.0 will decrease coverage by 0.43%.
The diff coverage is 92.3%.

@@            Coverage Diff             @@
##              2.0     #264      +/-   ##
==========================================
- Coverage   96.87%   96.43%   -0.44%     
==========================================
  Files           9        9              
  Lines         384      393       +9     
  Branches      124      126       +2     
==========================================
+ Hits          372      379       +7     
- Misses          3        4       +1     
- Partials        9       10       +1

Impacted Files	Coverage Δ
src/normalize-options.js	100% <100%> (ø)	⬆️
src/index.js	97.67% <100%> (-2.33%)	⬇️
src/targets-parser.js	96.29% <81.81%> (-0.07%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b2b3401...a18d636. Read the comment docs.

[nodkz]

@existentialism @yavorsky can you add a prefix to your deprecation messages?

I update dependencies, start a new production build and got such message:

Firstly I think that problem in new Webpack 3.5, but its and UglifyPlugin source code does not contain such massage. And look in my .babelrc.js and found targets.uglify: true for production build there.

in your code you use console.log, maybe you add wrapper over your messages deprecate, info, error etc?
Thanks.

[existentialism]

@nodkz 👍