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

Ansible

14K
11.2K
+ 1
1.3K
npm

69.4K
54.3K
+ 1
1.6K
Add tool

Ansible vs npm: What are the differences?

Developers describe Ansible as "Radically simple configuration-management, application deployment, task-execution, and multi-node orchestration engine". Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use. 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.

Ansible and npm are primarily classified as "Server Configuration and Automation" and "Front End Package Manager" tools respectively.

"Agentless", "Great configuration " and "Simple" are the key factors why developers consider Ansible; whereas "Best package management system for javascript", "Open-source" and "Great community" are the primary reasons why npm is favored.

Ansible and npm are both open source tools. Ansible with 38.2K GitHub stars and 16K forks on GitHub appears to be more popular than npm with 17.2K GitHub stars and 3.17K GitHub forks.

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

Advice on Ansible and npm
Needs advice
on
Puppet LabsPuppet LabsChefChef
and
AnsibleAnsible

I'm just getting started using Vagrant to help automate setting up local VMs to set up a Kubernetes cluster (development and experimentation only). (Yes, I do know about minikube)

I'm looking for a tool to help install software packages, setup users, etc..., on these VMs. I'm also fairly new to Ansible, Chef, and Puppet. What's a good one to start with to learn? I might decide to try all 3 at some point for my own curiosity.

The most important factors for me are simplicity, ease of use, shortest learning curve.

See more
Replies (2)
Recommends
AnsibleAnsible

I have been working with Puppet and Ansible. The reason why I prefer ansible is the distribution of it. Ansible is more lightweight and therefore more popular. This leads to situations, where you can get fully packaged applications for ansible (e.g. confluent) supported by the vendor, but only incomplete packages for Puppet.

The only advantage I would see with Puppet if someone wants to use Foreman. This is still better supported with Puppet.

See more
Gabriel Pa
Recommends
KubernetesKubernetes
at

If you are just starting out, might as well learn Kubernetes There's a lot of tools that come with Kube that make it easier to use and most importantly: you become cloud-agnostic. We use Ansible because it's a lot simpler than Chef or Puppet and if you use Docker Compose for your deployments you can re-use them with Kubernetes later when you migrate

See more
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 · 123.6K 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
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

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
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
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
tataata
Frontend designer and developer · | 3 upvotes · 111.4K 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
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
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
Tor Hagemann
Principal Software Engineer at Socotra · | 3 upvotes · 11.7K 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
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
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
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
Decisions about Ansible and npm
Oleksandr Fedotov
Senior Software Engineer at joyn · | 3 upvotes · 136K 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 · 145.9K 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 Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Ansible
Pros of npm
  • 276
    Agentless
  • 204
    Great configuration
  • 195
    Simple
  • 173
    Powerful
  • 151
    Easy to learn
  • 66
    Flexible
  • 54
    Doesn't get in the way of getting s--- done
  • 34
    Makes sense
  • 29
    Super efficient and flexible
  • 27
    Powerful
  • 11
    Dynamic Inventory
  • 8
    Backed by Red Hat
  • 7
    Works with AWS
  • 6
    Cloud Oriented
  • 6
    Easy to maintain
  • 4
    Because SSH
  • 4
    Multi language
  • 4
    Easy
  • 4
    Simple
  • 4
    Procedural or declarative, or both
  • 4
    Simple and powerful
  • 3
    Consistency
  • 3
    Vagrant provisioner
  • 2
    Fast as hell
  • 2
    Masterless
  • 2
    Well-documented
  • 2
    Merge hash to get final configuration similar to hiera
  • 2
    Debugging is simple
  • 1
    Work on windows, but difficult to manage
  • 1
    Certified Content
  • 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 Ansible
Cons of npm
  • 5
    Dangerous
  • 5
    Hard to install
  • 3
    Bloated
  • 3
    Backward compatibility
  • 2
    Doesn't Run on Windows
  • 2
    No immutable infrastructure
  • 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

What is Ansible?

Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.

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 Ansible?
What companies use npm?
See which teams inside your own company are using Ansible 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 Ansible?
What tools integrate with npm?

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

Blog Posts

PythonDockerKubernetes+14
11
2110
Node.jsnpmKubernetes+6
1
1164
GitHubGitSlack+30
25
15581
JavaScriptGitHubGit+33
20
1721
GitHubDockerAmazon EC2+23
12
6360
JavaScriptGitHubPython+42
52
19916
What are some alternatives to Ansible and npm?
Puppet Labs
Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.
Chef
Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others.
Salt
Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more.
Terraform
With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.
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.
See all alternatives