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

Azure DevOps

1.9K
2.1K
+ 1
232
npm

68K
52.4K
+ 1
1.6K
Add tool

Azure DevOps vs npm: What are the differences?

Developers describe Azure DevOps as "Services for teams to share code, track work, and ship software". Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support. On the other hand, npm is detailed as "The package manager for JavaScript". npm is the command-line interface to the npm ecosystem. It is battle-tested, surprisingly flexible, and used by hundreds of thousands of JavaScript developers every day.

Azure DevOps and npm are primarily classified as "Project Management" and "Front End Package Manager" tools respectively.

"Complete and powerful" is the primary reason why developers consider Azure DevOps over the competitors, whereas "Best package management system for javascript" was stated as the key factor in picking npm.

npm is an open source tool with 17.2K GitHub stars and 3.17K GitHub forks. Here's a link to npm's open source repository on GitHub.

According to the StackShare community, npm has a broader approval, being mentioned in 2644 company stacks & 2670 developers stacks; compared to Azure DevOps, which is listed in 79 company stacks and 68 developer stacks.

Advice on Azure DevOps and npm
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 (14)
Julian Sanchez
Lead Developer at Chore Champion · | 11 upvotes · 115.3K 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
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
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

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
Tor Hagemann
Principal Software Engineer at Socotra · | 3 upvotes · 3.5K views
Recommends
Yarn
npm

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
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
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
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
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
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
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
tataata
Frontend designer and developer · | 3 upvotes · 103.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
Decisions about Azure DevOps and npm
Oleksandr Fedotov
Senior Software Engineer at joyn · | 3 upvotes · 127.4K 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 · 137.3K views
Chose
Yarn
over
npm
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 Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Azure DevOps
Pros of npm
  • 49
    Complete and powerful
  • 29
    Huge extension ecosystem
  • 26
    Azure integration
  • 25
    One Stop Shop For Build server, Project Mgt, CDCI
  • 25
    Flexible and powerful
  • 15
    Everything I need. Simple and intuitive UI
  • 13
    Support Open Source
  • 8
    Integrations
  • 7
    GitHub Integration
  • 6
    One 4 all
  • 6
    Project Mgmt Features
  • 5
    Crap
  • 5
    Runs in the cloud
  • 5
    Cost free for Stakeholders
  • 3
    Agent On-Premise(Linux - Windows)
  • 2
    Aws integration
  • 2
    Jenkins Integration
  • 1
    GCP Integration
  • 649
    Best package management system for javascript
  • 383
    Open-source
  • 327
    Great community
  • 148
    More packages than rubygems, pypi, or packagist
  • 112
    Nice people matter
  • 6
    Audit feature
  • 5
    As fast as yarn but really free of facebook
  • 4
    Good following
  • 1
    Super fast
  • 1
    Stability

Sign up to add or upvote prosMake informed product decisions

Cons of Azure DevOps
Cons of npm
  • 6
    Still dependant on C# for agents
  • 4
    Capacity across cross functional teams not visibile
  • 4
    Half Baked
  • 3
    Not a requirements management tool
  • 3
    Poor Jenkins integration
  • 3
    Many in devops disregard MS altogether
  • 3
    Jack of all trades, master of none
  • 5
    Problems with lockfiles
  • 5
    Bad at package versioning and being deterministic
  • 3
    Node-gyp takes forever
  • 1
    Super slow

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is Azure DevOps?

Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.

What is npm?

npm is the command-line interface to the npm ecosystem. It is battle-tested, surprisingly flexible, and used by hundreds of thousands of JavaScript developers every day.

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

What companies use Azure DevOps?
What companies use npm?
See which teams inside your own company are using Azure DevOps or npm.
Sign up for Private StackShareLearn More

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

What tools integrate with Azure DevOps?
What tools integrate with npm?

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

Blog Posts

+6
1
1159
+42
52
19833
What are some alternatives to Azure DevOps and npm?
Jenkins
In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
AWS CodePipeline
CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define.
Jira
Jira's secret sauce is the way it simplifies the complexities of software development into manageable units of work. Jira comes out-of-the-box with everything agile teams need to ship value to customers faster.
Visual Studio
Visual Studio is a suite of component-based software development tools and other technologies for building powerful, high-performance applications.
See all alternatives