v0.28.1 Various bug fixes, minor feature

Yes! New Release!

• #669 Fixing postcss error: newer versions seem to have a "Syntax Error: name - this PR also removed 2 unused dependencies: lodash and fs-extra.

• #642 Allow to configure babel env preset (thanks to @ihmels)

• #639 bug #638 sass-loader should not do css minification (thanks to @wimhendrikx)

• #627 Allow to overwrite pre-defined aliases using addAliases() (thanks to @Lyrkan)

To upgrade, run yarn upgrade!

Changes: v0.28.0..v0.28.1

Documentation: http://symfony.com/doc/current/frontend.html

Happy packing!

v0.28.0 New options & less Babel transforms on production

Friends! A new release is here!

To upgrade:

1. Update your package.json file: set the @symfony/webpack-encore version to ^0.28.0.

2. Run yarn upgrade!

Changes: v0.27.0..v0.28.0

Documentation: http://symfony.com/doc/current/frontend.html

Highlights:

• Don't make @babel/preset-env use forceAllTransforms option
  in production - this will reduce build size in production
  for environments that only need to support more modern
  browsers - #612 thanks to @Lyrkan.

• Added support with enablePostCssLoader() to process files
  ending in .postcss or using lang="postcss" in Vue - #594
  thanks to @Lyrkan.

• Allow resolve-url-loader to be configured via enableSassLoader() -
  #603 thanks to @diegocardoso93.

• Support was removed from Node 9 (a no-longer-supported version
  of Node) - #585 thanks to @weaverryan

v0.27.0 Babel useBuiltIns bug fix & Vue JSX Support!

Zoinks! Another release is ready!

To upgrade:

1. Update your package.json file: set the @symfony/webpack-encore version to ^0.27.0.

2. Run yarn upgrade!

Changes: v0.26.0..v0.27.0

Documentation: http://symfony.com/doc/current/frontend.html

Highlights:

• [Behavior Change] The Babel configuration sourceType default was
  changed from not being specified (so, the default module was used)
  to unambiguous. This is to help Babel's useBuiltIns functionality
  properly determine if a require or import should be automatically
  added to your files, based on that file's style - #555 thanks to @Lyrkan.

• Added JSX support to Vue! #553 thanks to @Kocal.

• Cleaned up the jsdoc in index.js to add better docs and better
  IDE auto-completion - #550 thank sto @Lyrkan.

Happy packing!

v0.26.0 useBuiltIns Behavior change, style resolving & integrity support

We did it! Another release! 🥇

To upgrade:

1. Update your package.json file: set the @symfony/webpack-encore version to ^0.26.0.

2. Run yarn upgrade!

Changes: v0.25.0..v0.26.0

• [Behavior change] The Babel useBuiltIns option default value changed
  from entry to false, which means that polyfills may no longer be
  provided in the same way. This is due to a change in Babel and core-js.
  To get the same functionality back, run yarn add core-js --dev, then use:

  Encore.configureBabel(() => {}, {
      useBuiltIns: 'entry', // or try "usage"
      corejs: 3
  })

  This comes from #545 thanks to @Lyrkan.

• Added the ability to "resolve" CSS and Sass files without specifying
  the file extension and by taking advantage of the sass or style
  attribute in an npm package. For example, you can now import the main
  Bootstrap SASS file from within a SASS file by saying @import ~bootstrap.
  This will use the sass attribute from the bootstrap package.json
  file to find which file to load. #474 thanks to @deAtog.

• Added a new Encore.enableIntegrityHashes(), which will cause a new
  integrity key to be added to entrypoints.json with integrity values
  that can be included in the script or link tag for that asset - #522
  thanks to @Lyrkan.

• Allow some parts of configureBabel() to be used, even if there is
  an external .babelrc configuration file - #544 thanks to @Lyrkan.

v0.25.0 Upgraded dependencies, features, bug fixes

We did it! Another release!

To upgrade: yarn upgrade

Changes: v0.24.0..v0.25.0

Documentation: http://symfony.com/doc/current/frontend.html

Highlights:

• [BC BREAK] Various dependency versions were updated, including
  css-loader updated from ^1.0.0 to ^2.1.1 and resolve-url-loader
  updated from ^2.3.0 to ^3.0.1. The minimum Node version was
  also bumped from 6 to 8. See #540 for more details.

• Added Encore.disableCssExtraction() if you prefer your CSS to
  be output via the style-loader - #539 thank to @Lyrkan.

• Added Encore.configureLoaderRule() as a way to configure the
  loader config that Encore normally handles - #509 thanks to @Kocal.

• Babel cache is no longer used for production builds to avoid a
  bug where the cache prevents browserslist from being used - #516
  thanks to @Lyrkan.

v0.23.0 Faster builds, vue module support & more

Hi friends!

Ah, another nice release powered by the community!

Changes: v0.22.4..v0.23.0

Highlights:

• Add support for CSS modules in Vue - #508 thanks to @Lyrkan

• Store externals in an array - #495 thanks to @deAtog

• Add Encore.isRuntimeEnvironmentConfigured() - #500 thanks
  to @stof.

• Add the ability to configure watch options - #486 thanks
  to @Kocal

• Enabled cache and parallelism for terser for faster builds -
  #497 thanks to @Kocal

v0.22.4 - Fixing Vue + Typescript bug & other minor things

Yes! A new release - but just some minor fixes.

To upgrade: yarn upgrade

Changes: v0.22.3..v0.22.4

Documentation: http://symfony.com/doc/current/frontend.html

Highlights:

• #483 Add new methods isDev() and isDevServer() - thanks to @Kocal
• #484 Allow to import .vue files when using TypeScript - thanks to @Lyrkan
• #485 Fix small mistakes in shared-entry-concat-plugin.js and validator.js - thanks to @Lyrkan

v0.22.3 - Security release

A quick security release!

To upgrade: yarn upgrade

Changes: v0.22.2..v0.22.3

Documentation: http://symfony.com/doc/current/frontend.html

See #481 - this release guarantees that you are using a version of webpack-dev-server that does not contain the security issue.

v0.22.2: Important bug fixes to versioning & caching

This bug fix release includes several important changes that fix some versioning bugs and improve caching.

To upgrade: yarn upgrade

Changes: v0.22.1..v0.22.2

Highlights:

• Fix an issue where JavaScript files might change, but their versioning hash filename would NOT change - causing problems where users would use out-of-date cached assets, instead of dowloading the new ones. This works by, internall, using the names of modules in compiled files. This bug only affected users using enableSingleRuntimeChunk() - #462

• Fixed a bug where certain content changes to a JavaScript file would not cause the versioning hash to update. This relates to the first fixed bug. Due to the changing in how hashing works, all JavaScript files will have a new hash the first time after upgrading - #463

• Fixed a bug with splitEntryChunks() where some filenames and contents of files would change unnecessarily. This did not cause any bad behavior, but meant that users would unnecessarily download new assets, that really didn't need to change between builds. As a result, you'll notice that instead of split chunks named something like vendors~abc123.js, in production, they will be called 0.js or some other integer. This makes no functional difference - #462

v0.22.1 Bug fix for production sourcemaps

Just a bug fix release!

• Bug #454 was fixed, where a recent change made CSS sourcemaps always output in production.