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

answer-store

v0.4.0

Published

Store answers to user prompts, based on locale and/or current working directory.

Downloads

67

Readme

answer-store NPM version Build Status

Store answers to user prompts, based on locale and/or current working directory.

TOC

(TOC generated by verb using markdown-toc)

Install

Install with npm:

$ npm i answer-store --save

Usage

var answer = require('answer-store');

What does this do?

With project generators and build systems it's fairly common to prompt the user for information that is needed to complete the build or generate the project.

This library makes it easy to:

  1. Persist the answers to the file system
  2. Store values based on the current working directory
  3. Store defaults that can be used regardless of the directory

How this works

  • An answer is stored based on the current working directory, and the currently defined locale.
  • A default answer may be defined for each locale

See the API docs for information about setting and getting stores values.

Example

var answer = new Answer('project-name');
answer.set('foo');

Results in the following object being written to project-name.json at '/Users/jonschlinkert/answers/project-name.json':

{
  cache:
   { dest: '/Users/jonschlinkert/answers',
+     path: '/Users/jonschlinkert/answers/project-name.json',
     cwd: '/Users/jonschlinkert/dev/answer-store' },
  options: {},
  name: 'project-name',
  data: { 
    en: { 
      '/Users/jonschlinkert/dev/answer-store': 'foo' 
    }
  }
}

locales

If the question has been answered for multiple locales, the object would something like this:

{
  cache:
   { dest: '/Users/jonschlinkert/answers',
     path: '/Users/jonschlinkert/answers/project-name.json',
     cwd: '/Users/jonschlinkert/dev/answer-store' },
  options: {},
  name: 'project-name',
+  data: { 
+    en: { '/Users/jonschlinkert/dev/answer-store': 'foo' },
+    es: { '/Users/jonschlinkert/dev/answer-store': 'bar' },
+    fr: { '/Users/jonschlinkert/dev/answer-store': 'baz' }
+  }
}

directories

When the question has been answered from different directories, the object might look something like this:

{
  cache:
   { dest: '/Users/jonschlinkert/answers',
     path: '/Users/jonschlinkert/answers/project-name.json',
     cwd: '/Users/jonschlinkert/dev/answer-store' },
  options: {},
  name: 'project-name',
  data: { 
+    en: { 
+      '/Users/jonschlinkert/dev/answer-store/1': 'foo1',
+      '/Users/jonschlinkert/dev/answer-store/2': 'foo2',
+      '/Users/jonschlinkert/dev/answer-store/3': 'foo3' 
+    }
  }
}

defaults

A default value may be stored for each locale:

{
  cache:
   { dest: '/Users/jonschlinkert/answers',
     path: '/Users/jonschlinkert/answers/project-name.json',
     cwd: '/Users/jonschlinkert/dev/answer-store' },
  options: {},
  name: 'project-name',
  data: { 
+    default: 'foo',
    en: { 
      '/Users/jonschlinkert/dev/answer-store/1': 'foo1',
      '/Users/jonschlinkert/dev/answer-store/2': 'foo2',
      '/Users/jonschlinkert/dev/answer-store/3': 'foo3' 
    }
  }
}

What else?

Module dependencies are lazily required, so initialization is fast!

API

Answer

Create new Answer store name, with the given options.

Params

  • name {String}: The answer property name.
  • options {Object}: Store options

.set

Store the specified value for the current (or given) local, at the current cwd.

Params

  • value {any}: The answer value.
  • locale {String}: Optionally pass the locale to use, otherwise the default locale is used.

Example

answer.set('foo');

.get

Get the stored answer for the current (or given) locale at the current cwd.

Params

  • locale {String}: Optionally pass the locale to use, otherwise the default locale is used.

Example

answer.get(locale);

.has

Return true if an answer has been stored for the current (or given) locale at the working directory.

Params

  • locale {String}: Optionally pass the locale to use, otherwise the default locale is used.

Example

answer.has('foo');

.del

Delete the stored values for the current (or given) locale, at the current cwd.

Params

  • locale {String}: Optionally pass the local to delete.

Example

answer.del(locale);

.erase

Erase all stored values and delete the answer store from the file system.

Example

answer.erase();

.setDefault

Set the default answer for the currently defined locale.

Params

  • locale {String}: Optionally pass the locale to use, otherwise the default locale is used.

Example

answer.setDefault('foo');

.getDefault

Get the default answer for the currently defined locale.

Params

  • locale {String}: Optionally pass the locale to use, otherwise the default locale is used.

Example

answer.getDefault();

.hasDefault

Return true if a value is stored for the current (or given) locale, at the current cwd.

Params

  • locale {String}: Optionally pass the locale to use, otherwise the default locale is used.

Example

answer.hasDefault(locale);

.delDefault

Delete the stored values for the current (or given) locale.

Params

  • locale {String}: Optionally pass the local to delete.

Example

answer.delDefault(locale);

Related projects

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.

Building docs

Generate readme and API documentation with verb:

$ npm i -d && npm run docs

Or, if verb is installed globally:

$ verb

Running tests

Install dev dependencies:

$ npm i -d && npm test

Author

Jon Schlinkert

License

Copyright © 2016 Jon Schlinkert Released under the MIT license.


This file was generated by verb, v0.9.0, on February 21, 2016.