Alternatives to npm logo

Alternatives to npm

Yarn, gulp, Apache Maven, Bower, and NuGet are the most popular alternatives and competitors to npm.
21.9K
17.3K
+ 1
1.6K

What is npm and what are its top alternatives?

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.
npm is a tool in the Front End Package Manager category of a tech stack.
npm is an open source tool with 17.2K GitHub stars and 3.2K GitHub forks. Here’s a link to npm's open source repository on GitHub

npm alternatives & related posts

Yarn logo

Yarn

4.1K
2.8K
116
4.1K
2.8K
+ 1
116
A new package manager for JavaScript
Yarn logo
Yarn
VS
npm logo
npm

related Yarn posts

Johnny Bell
Johnny Bell
Senior Software Engineer at StackShare · | 17 upvotes · 476.8K views
Webpack
Webpack
Node.js
Node.js
Yarn
Yarn
npm
npm
Babel
Babel
Prettier
Prettier
ESLint
ESLint
#ES6
#ES5

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
npm
npm
Yarn
Yarn
#PackageManagers

#PackageManagers After a long time where npm failed to install packages and lot's of googling on answers, we switched to Yarn and alomost all those problems where solved. Today i mostly use "yarn add" instead of "npm install --save".

See more

related gulp posts

Tomáš Pustelník
Tomáš Pustelník
JavaScript
JavaScript
jQuery
jQuery
gulp
gulp
Webpack
Webpack

I use JavaScript these days and for few years I didn't have to use jQuery at all. I used to use it back in the days when IE8 and similar was a thing. But due to better browser support of native functions for DOM manipulation I could move to vanilla JavaScript. Most of the time, that's all I need to work with modals/accordions and similar. But I'm not saying that jQuery is bad. It was, and still is a great tool. Some of it's features are available in all browsers nowadays so it is not so important as it used to be. But jQuery has still advantage for example in it's selector engine, some DOM selections which are easy in jQuery are a bit more difficult in vanilla JS (you have to create some helper functions or use some 3rd party library to help you with that), but to be honest I needed this on very few occasions. So it really depends on your project (supported browses, plain JS or some bundling - gulp, Webpack, whether you plan to use modules etc.). Hope this helps.

See more
Gustavo Muñoz
Gustavo Muñoz
Web UI Developer at Globant · | 4 upvotes · 188.1K views
Webpack
Webpack
Grunt
Grunt
gulp
gulp
Parcel
Parcel
#Merge
#WebPackDevServer

Using Webpack is one of the best decision ever. I have used to Grunt and gulp previously, but the experience is not the same, and despite I know there are other bundlers like Parcel, Webpack gives me the perfect balance between automatization and configuration. The ecosystem of tools and loaders is amazing, and with WebPack #merge, you can modularize your build and define standard pieces to assemble different build configurations. I don't like processes where you cannot see their guts, and you have to trust in magic a little bit too much for my taste. But also I don't want to reinvent the wheel and lose too much time configuring my build processes. And of course, I love #WebPackDevServer and hot reloading.

See more

related Apache Maven posts

Tymoteusz Paul
Tymoteusz Paul
Devops guy at X20X Development LTD · | 17 upvotes · 652.2K views
Vagrant
Vagrant
VirtualBox
VirtualBox
Ansible
Ansible
Elasticsearch
Elasticsearch
Kibana
Kibana
Logstash
Logstash
TeamCity
TeamCity
Jenkins
Jenkins
Slack
Slack
Apache Maven
Apache Maven
Vault
Vault
Git
Git
Docker
Docker
CircleCI
CircleCI
LXC
LXC
Amazon EC2
Amazon EC2

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more
Ganesa Vijayakumar
Ganesa Vijayakumar
Full Stack Coder | Module Lead · | 15 upvotes · 710.1K views
Codacy
Codacy
SonarQube
SonarQube
React
React
React Router
React Router
React Native
React Native
JavaScript
JavaScript
jQuery
jQuery
jQuery UI
jQuery UI
jQuery Mobile
jQuery Mobile
Bootstrap
Bootstrap
Java
Java
Node.js
Node.js
MySQL
MySQL
Hibernate
Hibernate
Heroku
Heroku
Amazon S3
Amazon S3
Amazon RDS
Amazon RDS
Solr
Solr
Elasticsearch
Elasticsearch
Amazon Route 53
Amazon Route 53
Microsoft Azure
Microsoft Azure
Amazon EC2 Container Service
Amazon EC2 Container Service
Apache Maven
Apache Maven
Git
Git
Docker
Docker

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
Bower logo

Bower

3.8K
2.6K
927
3.8K
2.6K
+ 1
927
A package manager for the web
Bower logo
Bower
VS
npm logo
npm
NuGet logo

NuGet

96
52
0
96
52
+ 1
0
The package manager for .NET
    Be the first to leave a pro
    NuGet logo
    NuGet
    VS
    npm logo
    npm
    Node.js logo

    Node.js

    35.3K
    29.3K
    8K
    35.3K
    29.3K
    + 1
    8K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    Node.js logo
    Node.js
    VS
    npm logo
    npm

    related Node.js posts

    Nick Parsons
    Nick Parsons
    Director of Developer Marketing at Stream · | 34 upvotes · 435.5K views
    atStreamStream
    Stream
    Stream
    Go
    Go
    JavaScript
    JavaScript
    ES6
    ES6
    Node.js
    Node.js
    Babel
    Babel
    Yarn
    Yarn
    Python
    Python
    #FrameworksFullStack
    #Languages

    Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

    We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

    We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

    Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

    #FrameworksFullStack #Languages

    See more
    Nick Rockwell
    Nick Rockwell
    CTO at NY Times · | 29 upvotes · 560.5K views
    atThe New York TimesThe New York Times
    MySQL
    MySQL
    PHP
    PHP
    React
    React
    Apollo
    Apollo
    GraphQL
    GraphQL
    Node.js
    Node.js
    Kafka
    Kafka
    Apache HTTP Server
    Apache HTTP Server

    When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

    So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

    React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

    Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

    See more
    JSPM logo

    JSPM

    12
    7
    0
    12
    7
    + 1
    0
    Frictionless browser package management
      Be the first to leave a pro
      JSPM logo
      JSPM
      VS
      npm logo
      npm
      RequireJS logo

      RequireJS

      5.6K
      1.1K
      307
      5.6K
      1.1K
      + 1
      307
      JavaScript file and module loader
      RequireJS logo
      RequireJS
      VS
      npm logo
      npm
      Browserify logo

      Browserify

      457
      326
      260
      457
      326
      + 1
      260
      Browser-side require() the node.js way
      Browserify logo
      Browserify
      VS
      npm logo
      npm

      related Browserify posts

      Yunus ÖZCAN
      Yunus ÖZCAN
      Founder at Appitr · | 1 upvotes · 41K views
      atAppitrAppitr
      JavaScript
      JavaScript
      ES6
      ES6
      React Native
      React Native
      Monaco Editor
      Monaco Editor
      Browserify
      Browserify
      Webpack
      Webpack
      Sequelize
      Sequelize
      npm
      npm
      Node.js
      Node.js
      ExpressJS
      ExpressJS
      Babel
      Babel
      Flow (JS)
      Flow (JS)
      ESLint
      ESLint
      MobX
      MobX
      GraphQL
      GraphQL

      Appitr Run JavaScript ES6 with React Native in the browser built on Monaco Editor, Browserify Webpack Sequelize npm Node.js ExpressJS Babel Flow Type ESLint MobX GraphQL

      See more
      Component logo

      Component

      140
      84
      20
      140
      84
      + 1
      20
      Client package management for building better web applications
      Component logo
      Component
      VS
      npm logo
      npm
      pip logo

      pip

      55
      32
      0
      55
      32
      + 1
      0
      A package installer for Python
        Be the first to leave a pro
        pip logo
        pip
        VS
        npm logo
        npm
        Bundler logo

        Bundler

        41
        21
        0
        41
        21
        + 1
        0
        A consistent environment for tracking and installing gems and versions
          Be the first to leave a pro
          Bundler logo
          Bundler
          VS
          npm logo
          npm
          Verdaccio logo

          Verdaccio

          18
          14
          3
          18
          14
          + 1
          3
          A lightweight private npm proxy registry
          Verdaccio logo
          Verdaccio
          VS
          npm logo
          npm
          Duo logo

          Duo

          9
          11
          1
          9
          11
          + 1
          1
          A next-generation package manager for the front end
          Duo logo
          Duo
          VS
          npm logo
          npm
          Browserify-CDN logo

          Browserify-CDN

          5
          14
          0
          5
          14
          + 1
          0
          Browserify as a service
            Be the first to leave a pro
            Browserify-CDN logo
            Browserify-CDN
            VS
            npm logo
            npm
            Entropic logo

            Entropic

            1
            4
            0
            1
            4
            + 1
            0
            A federated package registry for anything
              Be the first to leave a pro
              Entropic logo
              Entropic
              VS
              npm logo
              npm
              Pika.dev logo

              Pika.dev

              1
              3
              0
              1
              3
              + 1
              0
              A JavaScript package registry for the modern web
                Be the first to leave a pro
                Pika.dev logo
                Pika.dev
                VS
                npm logo
                npm