v6.0.0

Removes the PostCSS configuration to allow individual projects to set up their own configuration and specify which plugins PostCSS should use during the build process.

Projects using this package should now provide their own PostCSS config by adding a postcss.config.js file in the root of the project.

Example:

// postcss.config.js

module.exports = {
  sourceMap: true,
  plugins: [require('tailwindcss'), require('autoprefixer')],
};

v5.2.0

Removes the use of MQPacker which was causing issues with media queries and CSS Grid.

v4.1.0

Independently hash chunks for better long-term caching.

v3.0.0

Updates to Webpack 3, enables scope hoisting, and fixes minification for CSS files.

Important: Make sure to upgrade to @dosomething.org/babel-config^2.0.0 when using this!

v2.0.1

Remove LodashWebpackPlugin from the default config. (#6)

v2.0.0

This release updates our Webpack config for Webpack 2! It includes a standalone developer build option, automatically hashed asset filenames & revision manifest, and much improved customization method powered by webpack-merge.

Upgrade Guide

Update Webpack and this config package:

"devDependencies": {
    "@dosomething/webpack-config": "^2.0.0",
   // ...
    "webpack": "^2.4.1",
    "webpack-dev-server": "^2.4.2"
}

Update your scripts in your application's package.json:

  "scripts": {
-    "start": "webpack",
+    "start": "NODE_ENV=development webpack --watch",
+    "build:dev": "NODE_ENV=development webpack",
     "build": "NODE_ENV=production webpack",
  }

By default, outputted files will all have hashes (like app-e403528026001172451e.js) to prevent caching issues. If you're using Laravel, you can use the mix() helper to get the versioned filename.

That's probably it! If you made an customizations to your config, you may need to update those as well.

v1.1.1

Fixes issue with inlining NODE_ENV for conditional dev/production builds.