Webpack 2, RC 7 (opens in new tab)

(github.com)

41 pointsjfmercer9y ago22 comments

22 comments

Thanks whoever posted this article!!! On behalf of the webpack core team, we thank everyone who's been using webpack 2 since beta, we are at the finish line for getting final release. :) stay tuned

ZenoArrow9y ago

What features does Webpack 2 offer over Webpack 1?

hughes9y ago

My favorite change is how configuration has been clarified. For example, see how loaders are configured now - instead of using a giant string delimited by special characters like this:

    'css-loader?modules-true!postcss-loader!sass-loader'

Loaders are configured with an ordered list:

    [
      {
        loader: 'css-loader',
        options: {
          modules: true
        }
      },
      {
        loader: 'postcss-loader'
      },
      {
        loader: 'sass-loader'
      }
    ]

It takes up way more space but it's also entirely clear what's happening.

More config changes are summarized here:

http://javascriptplayground.com/blog/2016/10/moving-to-webpa...

scrollaway9y ago

After having used both Webpack 1 and 2, my favorite feature is simply most of the insanity being gone.

I was hitting my head against my desk setting up npm and webpack 1 for almost 3 hours a couple of weeks ago. I then said fuck it, replaced them with yarn and webpack 2 respectively and all my issues were fixed.

Truly magical.

1 more reply

sametmax9y ago

I still wonder how come the first syntax was considered a good idea in the first place ?

Figuring how to configure webpack 1 (haven't tried 2) is crazy, and I don't understand how people able to construct such a complex tool that is currently unique on the market, and works so well, managed to design a conf settings that badly.

5 more replies

lommaj9y ago

System.import split-points for code splitting, generates bundles with dependencies for lazy loading by route (automatically code split react router routes). Should make progressive web apps and optimization easier.

k__9y ago

yes, best feature.

before you had to use systemjs and jspm or something.

1 more reply

jagger279y ago

Seems like the headline feature is tree-shaking to remove unused files.

Vevolut9y ago

Except in my experience (and others as well) the tree shaking hasn't been working.

2 more replies

apfel9129y ago

lots of refactoring/rewriting in/for ES6

https://gist.github.com/sokra/27b24881210b56bbaff7

ohstopitu9y ago

DOCUMENTATION (no seriously...stuff is more documented than 1)

omouse9y ago

not really looking forward to the release of webpack2, all it means is wrestling with existing webpack 1 configs (which are already fragile and difficult to deal with) to port them over.

I wonder if the performance has improved.

oveddan9y ago

Is there a list of all the changes for Webpack 2, or an upgrade guide?

insin9y ago

The new docs have an upgrade guide: https://webpack.js.org/guides/migrating/

j / k navigate · click thread line to collapse

22 comments

thelarkinn9y ago

Thanks whoever posted this article!!! On behalf of the webpack core team, we thank everyone who's been using webpack 2 since beta, we are at the finish line for getting final release. :) stay tuned

ZenoArrow9y ago

What features does Webpack 2 offer over Webpack 1?

hughes9y ago

My favorite change is how configuration has been clarified. For example, see how loaders are configured now - instead of using a giant string delimited by special characters like this:

    'css-loader?modules-true!postcss-loader!sass-loader'

Loaders are configured with an ordered list:

    [
      {
        loader: 'css-loader',
        options: {
          modules: true
        }
      },
      {
        loader: 'postcss-loader'
      },
      {
        loader: 'sass-loader'
      }
    ]

It takes up way more space but it's also entirely clear what's happening.

More config changes are summarized here:

http://javascriptplayground.com/blog/2016/10/moving-to-webpa...

scrollaway9y ago

After having used both Webpack 1 and 2, my favorite feature is simply most of the insanity being gone.

Truly magical.

1 more reply

sametmax9y ago

I still wonder how come the first syntax was considered a good idea in the first place ?

5 more replies

lommaj9y ago

k__9y ago

yes, best feature.

before you had to use systemjs and jspm or something.

1 more reply

jagger279y ago

Seems like the headline feature is tree-shaking to remove unused files.

Vevolut9y ago

Except in my experience (and others as well) the tree shaking hasn't been working.

2 more replies

apfel9129y ago

lots of refactoring/rewriting in/for ES6

https://gist.github.com/sokra/27b24881210b56bbaff7

ohstopitu9y ago

DOCUMENTATION (no seriously...stuff is more documented than 1)

omouse9y ago

not really looking forward to the release of webpack2, all it means is wrestling with existing webpack 1 configs (which are already fragile and difficult to deal with) to port them over.

I wonder if the performance has improved.

oveddan9y ago

Is there a list of all the changes for Webpack 2, or an upgrade guide?

insin9y ago

The new docs have an upgrade guide: https://webpack.js.org/guides/migrating/

j / k navigate · click thread line to collapse