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

command-line-config

v2.0.0

Published

`npm i command-line-config` > Breaking change in version 2: ESM style exports

Downloads

35

Readme

Command Line Config

Install

npm i command-line-config

Breaking change in version 2: ESM style exports

Usage

Quick and dirty loading/saving of JSON files.

import * as settings_access from 'command-line-config'
//or...
//import { load, save } from 'command-line-config'

let settings = settings_access.load('./some_file.json')
settings.dumb = false
settings_access.save(settings, './some_file.json')

All paths are interpreted relative to the current working directory.

If you don't specify a path to load, the module assumes the file was passed in via the command-line, like so: node your-script.js config-file.json

let settings = settings_access.load()
settings.wat = "WHERE DID YOU COME FROM"
settings_access.save(settings)

Which command-line argument will be interpreted as a file to be opened? The first one to resolve to an actual file, of course!

All file-system interactions are done synchronously, which means you most likely only want to be interacting with it when your app launches/terminates (which is the most likely use case anyway).

Written for ISoft Data Systems, licensed WTFPL.

Moved to GitHub at SVN revision 27057.