Need advice about which tool to choose?Ask the StackShare community!

Webpack

25.4K
17.5K
+ 1
751
Yarn

11K
7.5K
+ 1
141
Add tool

Webpack vs Yarn: What are the differences?

Developers describe Webpack as "A bundler for javascript and friends". A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff. On the other hand, Yarn is detailed as "A new package manager for JavaScript". Yarn caches every package it downloads so it never needs to again. It also parallelizes operations to maximize resource utilization so install times are faster than ever.

Webpack and Yarn are primarily classified as "JS Build Tools / JS Task Runners" and "Front End Package Manager" tools respectively.

"Most powerful bundler" is the top reason why over 307 developers like Webpack, while over 74 developers mention "Incredibly fast" as the leading cause for choosing Yarn.

Webpack and Yarn are both open source tools. It seems that Webpack with 49.8K GitHub stars and 6.27K forks on GitHub has more adoption than Yarn with 36.2K GitHub stars and 2.22K GitHub forks.

Airbnb, Instagram, and Pinterest are some of the popular companies that use Webpack, whereas Yarn is used by StackShare, Intuit, and Swat.io. Webpack has a broader approval, being mentioned in 2206 company stacks & 1338 developers stacks; compared to Yarn, which is listed in 623 company stacks and 528 developer stacks.

Advice on Webpack and Yarn
Needs advice
on
npm
and
Yarn

From a StackShare Community member: “I’m a freelance web developer (I mostly use Node.js) and for future projects I’m debating between npm or Yarn as my default package manager. I’m a minimalist so I hate installing software if I don’t need to- in this case that would be Yarn. For those who made the switch from npm to Yarn, what benefits have you noticed? For those who stuck with npm, are you happy you with it?"

See more
Replies (13)
Julian Sanchez
Lead Developer at Chore Champion · | 8 upvotes · 76.8K views
Recommends
Yarn
at

We use Yarn because it allows us to more simply manage our node_modules. It also simplifies commands and increases speed when installing modules. Our teams module download time was cut in half after switching from NPM to Yarn. We now require all employees to use Yarn (to prevent errors with package-lock.json and yarn.lock).

See more
Recommends
npm

I use npm since new version is pretty fast as well (Yarn may be still faster a bit but the difference isn't huge). No need for other dependency and mainly Yarn sometimes do not work. Sometimes when I want to install project dependencies I got error using Yarn but with npm everything is installed correctly.

See more
Mark Nelissen
Recommends
npm
npm

I use npm because I also mainly use React and TypeScript. Since several typings (from DefinitelyTyped) depend on the React typings, Yarn tends to mess up which leads to duplicate libraries present (different versions of the same type definition), which hinders the Typescript compiler. Npm always resolves to a single version per transitive dependency. At least that's my experience with both.

See more
Recommends
Yarn

p.s.

I am not sure about the performance of the latest version of npm, whether it is different from my understanding of it below. Because I use npm very rarely when I had the following knowledge.

------⏬

I use Yarn because, first, yarn is the first tool to lock the version. Second, although npm also supports the lock version, when you use npm to lock the version, and then use package-lock.json on other systems, package-lock.json Will be modified. You understand what I mean, when you deploy projects based on Git...

See more
Recommends
Yarn

As far as I know Yarn is a super module of NPM. But it still needs npm to run.

Yarn was developed by Facebook's guys to fix some npm issues and performance.

If you use the last version of npm most of this problem does not exist anymore.

You can choose the option which makes you more confortable. I like using yarn because I'm used to it.

In the end the packages will be the same. Just try both and choose the one you feel more confortable. :)

See more
Shuuji TAKAHASHI
Recommends
Yarn

I use Yarn because it outputs nice progress messages with cute emoji and installs packages quickly if the package is cached. Also, Yarn creates yarn.lock file which makes the developer use the consistent environment.

See more
Recommends
Yarn

I am a minimalist too. I once had issues with installing Nuxt.js using NPM so I had to install Yarn but I also found that the Dev experience was much better

See more
Izzur Zuhri
Recommends
npm

I use npm because it has a lot of community support and the performance difference with alternative tool is not so significant for me.

See more
tataata
Frontend designer and developer · | 2 upvotes · 65.3K views
Recommends
Yarn

Yarn made it painless for the team to sync on versions of packages that we use on the project <3

See more
Francois Leurent
Recommends
npm
at

We tend to stick to npm, yarn is only a fancy alternative, not 10x better. Using a self -hosted private repository (via sinopia/npm-mirror) make package locking (mostly) pointless.

See more
Recommends
npm

I use npm because its the official package manager for Node. It's reliability, security and speed has increased over time so the battle is over!

See more
Digital All
Recommends
npm

I use npm because its packaged with node installation and handles npm tokens in CI/CD tools for private packages/libraries.

See more
Denys Slipetskyy
Recommends
Yarn
at

I use Yarn because it process my dependencies way faster, predictable deps resolution order, upgrade-interactive is very handy + some Yarn specific features (workspaces, Plug’n’Play alternative installation strategy) ...

See more
View all (13)
Decisions about Webpack and Yarn
Aleksandr Filatov
Contract Software Engineer - Microsoft · | 0 upvote · 65.1K views
Why migrated?

I could define the next points why we have to migrate:

  • Decrease build time of our application. (It was the main cause).
  • Also jspm install takes much more time than npm install.
  • Many config files for SystemJS and JSPM. For Webpack you can use just one main config file, and you can use some separate config files for specific builds using inheritance and merge them.
See more

We mostly use rollup to publish package onto NPM. For most all other use cases, we use the Meteor build tool (probably 99% of the time) for publishing packages. If you're using Node on FHIR you probably won't need to know rollup, unless you are somehow working on helping us publish front end user interface components using FHIR. That being said, we have been migrating away from Atmosphere package manager towards NPM. As we continue to migrate away, we may publish other NPM packages using rollup.

See more
Oleksandr Fedotov
Senior Software Engineer at joyn · | 3 upvotes · 88K views

As we have to build the application for many different TV platforms we want to split the application logic from the device/platform specific code. Previously we had different repositories and it was very hard to keep the development process when changes were done in multiple repositories, as we had to synchronize code reviews as well as merging and then updating the dependencies of projects. This issues would be even more critical when building the project from scratch what we did at Joyn. Therefor to keep all code in one place, at the same time keeping in separated in different modules we decided to give a try to monorepo. First we tried out lerna which was fine at the beginning, but later along the way we had issues with adding new dependencies which came out of the blue and were not easy to fix. Next round of evolution was yarn workspaces, we are still using it and are pretty happy with dev experience it provides. And one more advantage we got when switched to yarn workspaces that we also switched from npm to yarn what improved the state of the lock file a lot, because with npm package-lock file was updated every time you run npm install, frequent updates of package-lock file were causing very often merge conflicts. So right now we not just having faster dependencies installation time but also no conflicts coming from lock file.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Webpack
Pros of Yarn
  • 309
    Most powerful bundler
  • 182
    Built-in dev server with livereload
  • 143
    Can handle all types of assets
  • 87
    Easy configuration
  • 20
    Laravel-mix
  • 4
    Overengineered, Underdeveloped
  • 2
    Webpack-Encore
  • 2
    Makes it easy to bundle static assets
  • 1
    Redundant
  • 1
    Better support in Browser Dev-Tools
  • 84
    Incredibly fast
  • 21
    Easy to use
  • 12
    Open Source
  • 10
    Can install any npm package
  • 7
    Works where npm fails
  • 5
    Workspaces
  • 2
    Incomplete to run tasks

Sign up to add or upvote prosMake informed product decisions

Cons of Webpack
Cons of Yarn
  • 11
    Hard to configure
  • 2
    Spaghetti-Code out of the box
  • 2
    SystemJS integration is quite lackluster
  • 2
    Loader architecture is quite a mess (unreliable/buggy)
  • 2
    Fire and Forget mentality of Core-Developers
  • 2
    No clear direction
  • 15
    Facebook
  • 6
    Sends data to facebook
  • 3
    Should be installed separately
  • 2
    Cannot publish to registry other than npm

Sign up to add or upvote consMake informed product decisions

What is Webpack?

A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.

What is Yarn?

Yarn caches every package it downloads so it never needs to again. It also parallelizes operations to maximize resource utilization so install times are faster than ever.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention Webpack and Yarn as a desired skillset
What companies use Webpack?
What companies use Yarn?
See which teams inside your own company are using Webpack or Yarn.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Webpack?
What tools integrate with Yarn?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Webpack and Yarn?
gulp
Build system automating tasks: minification and copying of all JavaScript files, static images. More capable of watching files to automatically rerun the task when a file changes.
Babel
Babel will turn your ES6+ code into ES5 friendly code, so you can start using it right now without waiting for browser support.
Parcel
Parcel is a web application bundler, differentiated by its developer experience. It offers blazing fast performance utilizing multicore processing, and requires zero configuration.
Browserify
Browserify lets you require('modules') in the browser by bundling up all of your dependencies.
Grunt
The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes. After you've configured it, a task runner can do most of that mundane work for you—and your team—with basically zero effort.
See all alternatives
How developers use Webpack and Yarn
Volkan Özçelik uses
Webpack

Webpack is the best bundler. Period.

Yes, it has a(n arguably) messy documentation, and a steep learning curve; but once you get the hang of it, there is nothing you cannot do with it.

Use it and you don’t have to use any other bundler at all.

It has a vivid ecosystem, and great plugin support.

Mick Dekkers uses
Yarn

Yarn is a wonderful alternative to the built-in npm command-line interface. Dependency installation is crazy fast, because it caches every package and performs operations in parallel.

Volkan Özçelik uses
Yarn

I prefer yarn instead of npm.

Both npm and yarn work great.

I don’t see any overwhelming reason to choose one over another.

I just like yarn, that’s it.

Alec Cunningham uses
Webpack

My preferred build tool; allows me to bundle my JSX, JS, CSS files for easy access and I can pass the bundle through my node server for server side rendering.

Kent Steiner uses
Webpack

Flexible building and compiling of source for browser consumption, mainly for JS, but experimenting a little with CSS (although I prefer StylusJS for CSS).

Andrew Gatenby uses
Webpack

We use this to optimise the delivery of the client-side for our revised Admin System, so it's able to be delivered to browsers as efficiently as possible.

Cameron Drake uses
Webpack

Webpack compiles files to bundles with source maps. Using Webpack you can use the latest features (ES6) and have it compiled to compliant js.

Ambar uses
Yarn

We use it in every JS project. Blazing fast package manager for node.js. Easy to use in Docker containers

Coolfront Technologies uses
Yarn

Used in Coolfront Mobile and "Charlie" (flat rate search engine) as packaging mechanism.

IVS uses
Yarn

We tend to stick to npm, yarn is only a fancy alternative, not 10x better.