StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Deployment
  4. Server Configuration And Automation
  5. Puppet Labs vs npm

Puppet Labs vs npm

OverviewDecisionsComparisonAlternatives

Overview

Puppet Labs
Puppet Labs
Stacks1.3K
Followers793
Votes227
GitHub Stars7.7K
Forks2.2K
npm
npm
Stacks137.4K
Followers82.2K
Votes1.6K
GitHub Stars17.6K
Forks3.0K

npm vs Puppet Labs: What are the differences?

npm: 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; Puppet Labs: Server automation framework and application. 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.

npm belongs to "Front End Package Manager" category of the tech stack, while Puppet Labs can be primarily classified under "Server Configuration and Automation".

"Best package management system for javascript" is the top reason why over 643 developers like npm, while over 45 developers mention "Devops" as the leading cause for choosing Puppet Labs.

npm and Puppet Labs are both open source tools. It seems that npm with 17.2K GitHub stars and 3.17K forks on GitHub has more adoption than Puppet Labs with 5.37K GitHub stars and 2.1K GitHub forks.

reddit, Instacart, and Coursera are some of the popular companies that use npm, whereas Puppet Labs is used by Uber Technologies, Twitch, and PayPal. npm has a broader approval, being mentioned in 2642 company stacks & 2666 developers stacks; compared to Puppet Labs, which is listed in 180 company stacks and 49 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Puppet Labs, npm

StackShare
StackShare

Apr 23, 2019

Needs adviceonNode.jsNode.jsnpmnpmYarnYarn

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?"

294k views294k
Comments
Mark
Mark

CTO at Gemsotec bvba

Apr 25, 2019

ReviewonReactReactTypeScriptTypeScriptYarnYarn

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.

251k views251k
Comments
Oleksandr
Oleksandr

Senior Software Engineer at joyn

Dec 7, 2019

Decided

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.

310k views310k
Comments

Detailed Comparison

Puppet Labs
Puppet Labs
npm
npm

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.

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.

Insight- Puppet Enterprise's event inspector gives immediate and actionable insight into your environment, showing you what changed, where and how by classes, nodes and resources.;Discovery- Puppet Enterprise delivers a dynamic and fully-pluggable discovery service that allows you to take advantage of any data source or real-time query results to quickly locate, identify and group cloud nodes.;Provisioning- Automatically provision and configure bare metal, virtual, and private or public cloud capacity, all from a single pane. Save time getting your cloud projects off the ground by reusing the same configuration modules you set up for your physical deployments.;Configuration Management- Puppet Enterprise's declarative, model-based approach automates repetitive tasks and eliminates configuration drift. You define the desired state of your infrastructure, and Puppet Enterprise enforces this state, freeing you to work on tougher projects.;Orchestration- Quickly deploy critical updates, like security patches, across hundreds of servers in seconds, or proactively initiate Puppet runs to update configurations and report changes. Puppet Enterprise allows you to orchestrate controlled, multi-step operations to targeted collections of nodes, giving you complete control over infrastructure changes.;Reporting- Get visibility into your infrastructure, browse resources, and view reports that help you manage your configuration. Puppet Enterprise provides node hardware and software inventory, Puppet run change reports, and node configuration graphs via the product's console or 3rd party APIs.
-
Statistics
GitHub Stars
7.7K
GitHub Stars
17.6K
GitHub Forks
2.2K
GitHub Forks
3.0K
Stacks
1.3K
Stacks
137.4K
Followers
793
Followers
82.2K
Votes
227
Votes
1.6K
Pros & Cons
Pros
  • 52
    Devops
  • 44
    Automate it
  • 26
    Reusable components
  • 21
    Dynamic and idempotent server configuration
  • 18
    Great community
Cons
  • 3
    Steep learning curve
  • 1
    Customs types idempotence
Pros
  • 648
    Best package management system for javascript
  • 382
    Open-source
  • 327
    Great community
  • 148
    More packages than rubygems, pypi, or packagist
  • 112
    Nice people matter
Cons
  • 5
    Bad at package versioning and being deterministic
  • 5
    Problems with lockfiles
  • 3
    Node-gyp takes forever
  • 1
    Super slow

What are some alternatives to Puppet Labs, npm?

Ansible

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.

Chef

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.

Terraform

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.

RequireJS

RequireJS

RequireJS loads plain JavaScript files as well as more defined modules. It is optimized for in-browser use, including in a Web Worker, but it can be used in other JavaScript environments, like Rhino and Node. It implements the Asynchronous Module API. Using a modular script loader like RequireJS will improve the speed and quality of your code.

Browserify

Browserify

Browserify lets you require('modules') in the browser by bundling up all of your dependencies.

Capistrano

Capistrano

Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows.

Salt

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.

Yarn

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.

Fabric

Fabric

Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks. It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution.

AWS OpsWorks

AWS OpsWorks

Start from templates for common technologies like Ruby, Node.JS, PHP, and Java, or build your own using Chef recipes to install software packages and perform any task that you can script. AWS OpsWorks can scale your application using automatic load-based or time-based scaling and maintain the health of your application by detecting failed instances and replacing them. You have full control of deployments and automation of each component

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana