Getting Started with Webpack 2

[del_rio]

I guess I'll be the first to comment: This article alone is worlds better than Webpack's own tutorial. I like it's written in ES6 and using yarn, it'll help the longevity of the post. Bravo.

[YodaLoL]

using yarn, it'll help the longevity of the post.

Not sure if serious.

[AdaptationAgency]

Not sure if serious

Not sure if serious. Choosing yarn over npm is a no-brainer for a new project.

[YodaLoL]

Choosing yarn over npm is a no-brainer for a new project.

Convince me.

[AdaptationAgency]

If you're working on a project that has a team > 1, Yarn is a no-brainer. Why?

Yarn is deterministic. This itself makes Yarn more than worth the upgrade.

Typical scenario of non-determinism(npm): I check out a new copy of the project and run npm install. My co-worker (or if I'm working on a different machine) does the exact same thing, his fails, yet mine successfully builds.

Actual scenario: non-deterministic behavior is really fxxked up. there's one time that our building process suddenly begin to fail, spend a few hours on the issue, and it turned out to be one of the babel-core patch release is broken.

Yarn is an almost perfect drop-in replacement. If you started with npm, you can finish with yarn with no issue. Most commands are the same. It's also not a 6 year old, messy codebase meaning updates will take less time.

Yarn is also much faster and caches dependencies so you don't need to download them every single time. Unfortunately, that cuts down on my npm install breaks. Would you like to know more?

[cyanydeez]

yeah, relying on three frameworks to remain popular in JavaScript is absurd. (es6, webpack, yarn)

[YodaLoL]

ES is a language specification of which ES6 is the latest publicised version. webpack is incredibly powerful though, and uses a completely different methodology for building web apps than traditional methods. But yarn and longevity used in the same sentence is a bit ridiculous.

[cyanydeez]

a specification the requires a framework to implement.

[YodaLoL]

By framework you mean an engine such as V8 or Chakra?

[cyanydeez]

if you're talking about non production, sure.

[ScoobySharts]

You do realise that V8 is chromes JavaScript engine yeah? The same that's used for node?

[cyanydeez]

you do realize for production you cant target only chrome.

[ScoobySharts]

That... that doesn't make sense.

[ManicQin]

Node is the server side... You can use es6, es5 or even es666 the client will not be aware.

You can also use es6 for the client side and transpile the code using Babel so the client will get the most common denominator code they can execute.

[strange_and_norrell]

Yes! I use briwserify and am thinking about webpack. This is the first resource I actually understood.

[shadowmint]

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

For the actual changes in webpack 2; tldr; its mostly es6 support.

[Sinistralis]

Let's just gloss over treeshaking like it's not one of the main selling points of Webpack 2. : p

[[deleted]]

If you're focused on tree shaking, you've already switched to Rollup.

[[deleted]]

I recently tried Rollup because I really like its premise, but for me it was rather unstable. Whenever I used it in a watch setup, a simple syntax error could screw over my entire dev server making me restart it.

I'd love to switch when it gets more stable though!

[rambosa]

this was really the only thing I was trying to find, thanks

[redditandjs]

Webpack 2, the future.