New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More

@blinkmobile/blinkmrc

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@blinkmobile/blinkmrc

bit like https://github.com/yeoman/configstore but with home-directory and project-specific files

1.0.0
Version published
Weekly downloads
6
Maintainers
1
Weekly downloads
 
Created

blinkmrc.js

bit like https://github.com/yeoman/configstore but with home-directory and project-specific files

npm module Build Status

We extracted this from blinkmobile/bmp-cli for the benefit of our other CLI projects.

What is this?

This is a basic configuration file management library, hardcoded with defaults that suit our purposes. Like git and npm, this library straddles configuration files in 2 locations:

  • your home directory (based on your operating system), where files are readable by the current user and inaccessible by other users

  • your project directory, where files are readable by anyone with access to the project (i.e. if you version control these files with your project)

This pair of configuration files are both JSON-formatted.

By default we use the following filenames (but this is configurable):

  • user: blinkmrc.json

  • project: .blinkmrc.json (like .eslintrc.json or .travis.yml)

API

const blinkmrc = require('@blinkmobile/blinkmrc');
const pkg = require('./package.json');

userConfig (options: ConfigOptions) => ConfigStore

const userConfig = blinkmrc.userConfig({ name: pkg.name, /* ... */ });
UserConfigOptions
interface ConfigOptions {
  userConfigDir?: String,
  ...ConfigOptions
}

project (options: ConfigOptions) => ConfigStore

const projectConfig = blinkmrc.projectConfig({ name: pkg.name, /* ... */ });
ProjectConfigOptions
interface ConfigOptions {
  cwd = process.cwd(): String,
  ...ConfigOptions
}

ConfigOptions

interface ConfigOptions {
  name: String,
  filename = 'blinkmrc.json': String
}

ConfigStore

interface ConfigStore {
  load () => Promise[Object],
  update (updater: UpdaterFunction) => Promise,
  write () => Promise
}
load () => Promise[Object]

Locate the configuration file. If found, parse it as JSON and return the Object. If not found:

  • userConfig: return a new Object

  • projectConfig: reject with an Error

update (updater: UpdaterFunction) => Promise[Object]

Load the configuration data as above. Then pass it to the provided UpdaterFunction. Write the result of the UpdaterFunction back to the configuration file.

UpdaterFunction (config: Object) => Object

This function receives the current configuration data. This function may or may not change this data (as you determine) before returning it.

write (config: Object) => Promise[Object]

Store the provided configuration data in the appropriate file.

FAQs

Package last updated on 19 Feb 2016

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts