Webpack Babel Multi Target Plugin Versions Save

A Webpack plugin that works with Babel to allow differential loading - production deployment of ES2015 builds targeted to modern browsers, with an ES5 fallback for legacy browsers.

v2.5.0

3 years ago

Note: v2.4.0 is skipped due to a prerelease versioning conflict.

Added:

  • add support for HtmlWebpackPlugin v4 beta (#55, thanks @Austaras and @erezvish)
  • feat: add inject(head|body) and minify options to safari10NoModuleFix (#63, thanks @despian!)
  • feat: add preset configuration to babel options (#59, thanks @semoal!)

Fixed:

  • fix: Add exclude for 'querystring-es3 (#62, thanks again @despian!)
  • fix Angular Routing example

Updated

  • Bump html-webpack-plugin peerDependency requirement to ^3.2.0 || ^4.0.0

v2.5.0-next.3

3 years ago

Updated

  • Bump html-webpack-plugin peerDependency requirement to ^3.2.0 || ^4.0.0

v2.5.0-next.2

4 years ago

Note: 2.4.0 is skipped due to a prerelease versioning conflict.

Added:

  • feat: add inject(head|body) and minify options to safari10NoModuleFix (#63, thanks @despian!)
  • feat: add preset configuration to babel options (#59, thanks @semoal!)

Fixed:

  • fix: Add exclude for 'querystring-es3 (#62, thanks again @despian!)

See also: v2.5.0-next.1

v2.5.0-next.1

4 years ago

Note: 2.4.0 is skipped due to a prerelease versioning conflict.

  • add support for HtmlWebpackPlugin v4 beta (#55, thanks @Austaras and @erezvish)
  • fix Angular Routing example

v2.3.3

4 years ago
  • FIX: revert unintended corejs bump (#49, thanks to @aaarichter)
  • FIX: correctly handle packageName: false in package.json browser object (#51, thanks to @shurygindv)

v2.3.3-next.0

4 years ago

v2.3.3-next.1

4 years ago

v2.3.3-next.2

4 years ago

v2.3.3-next.3

4 years ago

v2.3.1

4 years ago
  • fix exclusion not working as advertised (#38, thanks @foglerek)
  • fix standard/known transpiling exclusions not using OS-specific path separators (#39)

Update:

  • A version bump to core-js that was planned for an upcoming release somehow managed to sneak into this one. I'm planning on reverting that commit and releasing a fix for the next patch release. My apologies for any inconvenience, and thanks to @aaarichter for reporting in #49