npm vs. RequireJS vs. Browserify

Dependency tracking for libraries. Publish this service as module for easy installation in a productive environment.

I use npm to fond great tools to create code and deploy it fastly and cool.

Handles our dev dependencies and all our API module dependencies.

Used to install packages our client-side app depends on.

Manage dependencies such as grunt and all its plugins. Also, in the API server, manages Loopbacks dependencies and ours.

We use NPM to manage third-party dependencies.

Used to manage Grunt and some build pipeline packages, such as imagemin.

Favorite package manager for javascript libraries.

Package management

We manage packages using NPM.

front-end / back-end package manager.

We use npm because everyone else does.

Build config page using numerous npm packages.

If you're using Node or Gulp, you can't help but use NPM in some form or another. Fortunately that's never a bad thing with the massive package repository and glowing ecosystem making it a breeze to work with.

Utilize npm private module to package shared library for different React / React Native clients. Shareable code goes here. Basically deliver Redux Store with Firebase integration and business logic in a library. Each React app utilizes this while delivering a device/target specific UI.

Front and backend package manager.

Package manager; dependency for Bower and Gulp in build pipeline.

The way most people use it.. npm install blah blah ;-)

Provides the node package management.

node.js modules management

"It just works (TM)"

npm is used both for our Node.js servers and our UI dependencies.

Package Dependencies for many front-end tools.

She always become reliable when I need it

Maintains java script libraries versions.

Back-end package manager, keeps the builds building _and _the files filing.

Back-end package manager.

Used as a dependency management tool.

Client and API javascript library management

Manages dependencies and build scripts.

To install of the project packages for the server.

Package manager for Angular2 App.

Most popular Javascript package manager in the world - used for all dependencies and Javascript packages.

lots of node modules for assets

JavasScript makes no sense without it

Used npm for pull-in modules for nodejs development.

package manager, and task runner.

Task runner for building, serving and deploying

npm is the app's primary package manager.

Package manager for node

NPM is used for server and client dependencies (client deps are compiled via babel)

How can you not use npm :-)

Module is published as bpost on the npm registry. Tasks for the module are also defined as npm run tasks with commit hooks for git

We manages all of our packages, including Angular JS through npm. It is a very quick way of downloading / installing packages into your project.

Node.JS package management

Used for package management.

our project manager

Dependency manager

npm? what's that ? :)

use for front-end development libraries. works well with gulp.

Used to manage packages.

For easy package management on client and server.

Great ecosystem of libraries and modules, and easy management of application resources.

Package관리가 이렇게 편리해질수 있다는 것을 알게 해주었습니다.

Package management for node dependencies

Great package manager.

자바스크립트를 위한 최고의 패키지 매니저. 더 이상의 설명은 필요하지 않다.

노드 모듈 관리는 npm을 사용합니다.

Package management.

Used for project package management.

The Twit, .envs, and Clarifai packages are currently the major packages used for the bot

You have package for everything

Add plugins for mobile project

front를 할땐 거의 npm 이죠

yarn으로 갈아탈 수 있습니다

Gerenciar as dependências do projeto

Node js? Then NPM!

Import libraries

Downloading frontend dependencies, like jquery, laravel mix...

It's the front-end version of Composer, so is pretty essential to pull in packages that can be tracked and kept up to date.

I like to manage my packages as simple as possible... npm i -g npm. Whoa! npmception?

Command Line Interface (CLI) http://www.npmjs.com/

Vast community.

The PrometheanTV platform relies heavily on the NodeJS platform and it's NPM package management system.

Manage packages used on mobile app.

Came With App

Used Require.js to make the application modular. It provides better dependency management with asynchronous loading of scripts.

Used to declare third-party dependencies for our client-side app.

Will be replaced with SystemJS soon.

Very nice way to structure a project, as long as you know it will not be a hybrid app.

For the server-side requirements of the project.

前端有了你，才像个样

No real definitive reason, I find it to be the most natural way to import libraries and code in nodejs (prior to ES6 / import).

JS 加载器

All frontends use this framework except new mobile experience.

Just use browserify & commonJS. We don't use RequireJS.

The RequireJS package manager is used by various web applications and services to manage dependencies on 3rd party libraries.

We use Browserify to keep our JS organized by requiring modules.

easy build a front end & back end usage code

Main React functionality pipeline broken into CommonJS modules: Reflux data stores, React components (cjsx - coffee/jsx).

Made sharing node modules with the frontend real easy. Especially when developing hybrid apps.

With Browserify we could create the inspector snippet used to connect the user's devices with the Dashboard. Using CommonJS modules we could organize large amounts of code alongside third-party JavaScript modules.

To cram all the .js into one huge bundle.

Used to build the Chrome/Firefox extensions and the bookmarklet.

It's the lesser of all of the other evils out there. Webpack makes you completely blind to how things are put together. I like gulp, this made it easy.