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 🙏

© 2026 – Pkg Stats / Ryan Hefner

remote-config

v1.0.0

Published

A simple way to get remote config files

Readme

remote-config

Build Status codecov Dependency Status

A small tool to get remote configuration files (.eslintrc, etc)

Disclaimer :

This module is provided as is, I decline any responsability for any consequences, wrong doing, unexpected effects linked in any way to the usage of the aforementioned module.

This module shoudn't be considered as production-ready.

Usage :

remote-config [OPTIONS]

Options :

--config=package.json // default: "package.json"

Define what JSON file will contain remote config files URLs

--key=remote-config // default: "remote-config"

Define where to look inside the configuration file

--overwrite=[true|false] // default: true

Whether the fetched file will be overwritten locally or not. Incompatible with recursive (should be compatible in future release)

--verbose=[true|false] // default: true

Self explanatory

--recursive=[true|false] // default: false

Whether to use each fetched file as a configuration file. Usefull for nested remote configuration files.

Minimalistic config file

Remote-config will look in the defined config file for the "remote-config" key, containing pairs such as "filepath_to_write": "url_to_fetch".

{
  "remote-config": {
    ".babelrc": "https://raw.githubusercontent.com/lagora/remote-config/master/.babelrc"
  }
}

Alternative syntax (for future usage)

{
  "remote-config": {
    ".babelrc": {
      "url": "https://raw.githubusercontent.com/lagora/remote-config/master/.babelrc"
    }
  }
}

Tips ?

You can, obviously, use remote-config to download a file containing various other config files. So you'll had to only remember one url, go figure.