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

pre-commit

409
39
+ 1
0
Yarn

16.4K
10.5K
+ 1
143
Add tool

pre-commit vs Yarn: What are the differences?

pre-commit: A slightly improved pre-commit hook for git. pre-commit checks your code for errors before you commit it. pre-commit is configurable; Yarn: 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.

pre-commit and Yarn are primarily classified as "Git" and "Front End Package Manager" tools respectively.

pre-commit and Yarn are both open source tools. Yarn with 36.2K GitHub stars and 2.22K forks on GitHub appears to be more popular than pre-commit with 756 GitHub stars and 96 GitHub forks.

Advice on pre-commit and Yarn
Needs advice
on
npmnpm
and
YarnYarn

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 (14)
Julian Sanchez
Lead Developer at Chore Champion · | 11 upvotes · 163.1K views
Recommends
YarnYarn
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
npmnpm

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
Recommends
YarnYarn

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
Mark Nelissen
Recommends
npmnpmnpmnpm

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
YarnYarn

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
YarnYarn

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
YarnYarn

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
Recommends
npmnpm

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
tataata
Frontend designer and developer · | 3 upvotes · 150K views
Recommends
YarnYarn

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

See more
Tor Hagemann
Principal Software Engineer at Socotra · | 3 upvotes · 50.3K views
Recommends
YarnYarnnpmnpm

You should use whichever had the best DX (developer experience) for your team. If you are doing a massive front-end project, consider yarn if not only because it makes it a snap to go from zero to ready. What some people say about npm being more stable or easier for smaller projects is highly true as well. (not to mention, you sometimes have to install yarn) But, note that official NodeJS Docker images ship with both npm and yarn. If you want to use yarn, put package-lock=false and optionally save-exact=true in your project's .npmrc file. Compare whether you prefer the ergonomics of yarn global add over npm install -g or see fewer meaningless warnings for the specific set of dependencies you leverage.

See more
Digital All
Recommends
npmnpm

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
YarnYarn
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
Izzur Zuhri
Recommends
npmnpm

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
Francois Leurent
Recommends
npmnpm
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
Decisions about pre-commit and Yarn
Oleksandr Fedotov
Senior Software Engineer at joyn · | 3 upvotes · 178.9K 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
Petr Bambušek
Head of Frontend at Mews · | 2 upvotes · 189K views
Chose
YarnYarn
over
npmnpm
at
()

This was no real choice - we switched the moment Yarn was available, and never looked back. Yarn is the only reasonable frontend package manager that's actually being developed. They even aim to heal the node_modules madness with v2! Npm is just copying its ideas on top of introducing massive bugs with every change.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of pre-commit
Pros of Yarn
    Be the first to leave a pro
    • 84
      Incredibly fast
    • 21
      Easy to use
    • 12
      Open Source
    • 10
      Can install any npm package
    • 7
      Works where npm fails
    • 6
      Workspaces
    • 2
      Incomplete to run tasks
    • 1
      Fast

    Sign up to add or upvote prosMake informed product decisions

    Cons of pre-commit
    Cons of Yarn
      Be the first to leave a con
      • 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 pre-commit?

      pre-commit checks your code for errors before you commit it. pre-commit is configurable.

      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!

      What companies use pre-commit?
      What companies use Yarn?
      See which teams inside your own company are using pre-commit or Yarn.
      Sign up for StackShare EnterpriseLearn More

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

      What tools integrate with pre-commit?
      What tools integrate with Yarn?
        No integrations found

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

        Blog Posts

        What are some alternatives to pre-commit and Yarn?
        hub
        hub is a command line tool that wraps git in order to extend it with extra features and commands that make working with GitHub easier.
        Git Flow
        It provides excellent command line help and output. It is a merge based solution. It doesn't rebase feature branches.
        Atlassian Stash
        It is a centralized solution to manage Git repositories behind the firewall. Streamlined for small agile teams, powerful enough for large organizations.
        Diff So Fancy
        diff-so-fancy builds on the good-lookin' output of git contrib's diff-highlight to upgrade your diffs' appearances.
        TortoiseGit
        It is a Git revision control client, implemented as a Windows shell extension and based on TortoiseSVN. It is free software released under the GNU General Public License.
        See all alternatives