npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

npm-dependencies-merge

v1.0.5

Published

Merges dependencies from multiple package.json files.

Downloads

10

Readme

npm-dependencies-merge

npm-dependencies-merge is a nifty little script that scans subdirectories searching for nested package.json files, and merges all the dependencies together in a single package.json file that is outputted to stdout.

A base template passed through standard input is used to produce the root package.json file. This allows package.json to be ignored by version control systems, which conflict with auto-generated files. Base package attributes, like name and version, can be stored in a separate file such as package-base.json, and kept in version control.

Example

$ cd project_directory
$ npm-dependencies-merge < package-base.json > package.json

Installation

$ npm install -g npm-dependencies-merge

Command line options

-h, --help           output usage information
-V, --version        output the version number
-s, --silent         do not print out warnings
-c, --combine        combine dependencies and devDependencies
-f, --files          files to search for (Default: package.json)
-o, --output [file]  output to a file

Conflicts

npm-dependencies-merge will warn you about any potential conflicts of the versions declared in the multiple package.json files