Alternatives to pnpm logo

Alternatives to pnpm

npm, Yarn, Lerna, Composer, and Homebrew are the most popular alternatives and competitors to pnpm.
16
13
+ 1
0

What is pnpm and what are its top alternatives?

It uses hard links and symlinks to save one version of a module only ever once on a disk. When using npm or Yarn for example, if you have 100 projects using the same version of lodash, you will have 100 copies of lodash on disk. With pnpm, lodash will be saved in a single place on the disk and a hard link will put it into the node_modules where it should be installed.
pnpm is a tool in the Package Managers category of a tech stack.
pnpm is an open source tool with 11.6K GitHub stars and 301 GitHub forks. Here鈥檚 a link to pnpm's open source repository on GitHub

Top Alternatives to pnpm

  • npm

    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. ...

  • 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. ...

  • Lerna

    Lerna

    It is a popular and widely used package written in JavaScript. It optimizes the workflow around managing multi-package repositories with git and npm. ...

  • Composer

    Composer

    It is a tool for dependency management in PHP. It allows you to declare the libraries your project depends on and it will manage (install/update) them for you. ...

  • Homebrew

    Homebrew

    Homebrew installs the stuff you need that Apple didn鈥檛. Homebrew installs packages to their own directory and then symlinks their files into /usr/local. ...

  • NuGet

    NuGet

    A free and open-source package manager designed for the Microsoft development platform. It is also distributed as a Visual Studio extension. ...

  • Nix

    Nix

    It makes package management reliable and reproducible. It provides atomic upgrades and rollbacks, side-by-side installation of multiple versions of a package, multi-user package management and easy setup of build environments. ...

  • fpm

    fpm

    It helps you build packages quickly and easily (Packages like RPM and DEB formats). ...

pnpm alternatives & related posts

npm logo

npm

60.6K
46.3K
1.6K
The package manager for JavaScript.
60.6K
46.3K
+ 1
1.6K
PROS OF NPM
  • 649
    Best package management system for javascript
  • 382
    Open-source
  • 327
    Great community
  • 147
    More packages than rubygems, pypi, or packagist
  • 112
    Nice people matter
  • 5
    Audit feature
  • 4
    Good following
  • 4
    As fast as yarn but really free of facebook
  • 1
    Stability
  • 1
    Super fast
CONS OF NPM
  • 5
    Problems with lockfiles
  • 5
    Bad at package versioning and being deterministic
  • 3
    Node-gyp takes forever
  • 1
    Super slow

related npm posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH | 24 upvotes 路 1.7M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API鈥檚 resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
Johnny Bell
Software Engineer at Weedmaps | 19 upvotes 路 1.2M views

So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

See more
Yarn logo

Yarn

10.7K
7.7K
141
A new package manager for JavaScript
10.7K
7.7K
+ 1
141
PROS OF YARN
  • 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
CONS OF YARN
  • 15
    Facebook
  • 6
    Sends data to facebook
  • 3
    Should be installed separately
  • 2
    Cannot publish to registry other than npm

related Yarn posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH | 24 upvotes 路 1.7M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API鈥檚 resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
Johnny Bell
Software Engineer at Weedmaps | 19 upvotes 路 1.2M views

So when starting a new project you generally have your go to tools to get your site up and running locally, and some scripts to build out a production version of your site. Create React App is great for that, however for my projects I feel as though there is to much bloat in Create React App and if I use it, then I'm tied to React, which I love but if I want to switch it up to Vue or something I want that flexibility.

So to start everything up and running I clone my personal Webpack boilerplate - This is still in Webpack 3, and does need some updating but gets the job done for now. So given the name of the repo you may have guessed that yes I am using Webpack as my bundler I use Webpack because it is so powerful, and even though it has a steep learning curve once you get it, its amazing.

The next thing I do is make sure my machine has Node.js configured and the right version installed then run Yarn. I decided to use Yarn because when I was building out this project npm had some shortcomings such as no .lock file. I could probably move from Yarn to npm but I don't really see any point really.

I use Babel to transpile all of my #ES6 to #ES5 so the browser can read it, I love Babel and to be honest haven't looked up any other transpilers because Babel is amazing.

Finally when developing I have Prettier setup to make sure all my code is clean and uniform across all my JS files, and ESLint to make sure I catch any errors or code that could be optimized.

I'm really happy with this stack for my local env setup, and I'll probably stick with it for a while.

See more
Lerna logo

Lerna

158
87
0
A tool for managing JavaScript projects
158
87
+ 1
0
PROS OF LERNA
    Be the first to leave a pro
    CONS OF LERNA
      Be the first to leave a con

      related Lerna posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH | 24 upvotes 路 1.7M views

      Our whole Node.js backend stack consists of the following tools:

      • Lerna as a tool for multi package and multi repository management
      • npm as package manager
      • NestJS as Node.js framework
      • TypeScript as programming language
      • ExpressJS as web server
      • Swagger UI for visualizing and interacting with the API鈥檚 resources
      • Postman as a tool for API development
      • TypeORM as object relational mapping layer
      • JSON Web Token for access token management

      The main reason we have chosen Node.js over PHP is related to the following artifacts:

      • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
      • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
      • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
      • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
      See more
      Composer logo

      Composer

      765
      419
      13
      Dependency Manager for PHP
      765
      419
      + 1
      13
      PROS OF COMPOSER
      • 7
        Must have dependency manager for PHP
      • 3
        Centralized autoload.php
      • 3
        Large number of libraries
      CONS OF COMPOSER
        Be the first to leave a con

        related Composer posts

        Homebrew logo

        Homebrew

        406
        346
        1
        The Missing Package Manager for macOS
        406
        346
        + 1
        1
        PROS OF HOMEBREW
        • 1
          Clean, neat, powerful, fast and furious
        CONS OF HOMEBREW
          Be the first to leave a con

          related Homebrew posts

          NuGet logo

          NuGet

          182
          111
          0
          The package manager for .NET
          182
          111
          + 1
          0
          PROS OF NUGET
          • 0
            Best package (and maybe only 1) management for .NET
          CONS OF NUGET
            Be the first to leave a con

            related NuGet posts

            Nix logo

            Nix

            83
            43
            0
            A package manager for Linux and other Unix systems
            83
            43
            + 1
            0
            PROS OF NIX
              Be the first to leave a pro
              CONS OF NIX
                Be the first to leave a con

                related Nix posts

                fpm logo

                fpm

                69
                80
                2
                packaging made simple
                69
                80
                + 1
                2
                PROS OF FPM
                • 2
                  Easy to use
                CONS OF FPM
                  Be the first to leave a con

                  related fpm posts