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

value-box

v0.12.0

Published

Enum like project values.

Downloads

17

Readme

Value Box

Json, Js and Yaml as plain old JavaScript all in one place.

ValueBox has two sets of values:

  • Presets: Ready to use values
  • Extended: Loaded from json, yaml or js files.

Preset values

Without any config, ValueBox provides a few values out of the box:

  • HTTP
    • Methods: [GET, POST, PUT, DELETE]
    • Status Codes
  • Application Environments: DEV, PROD, TEST
  • Mongoose Connection Status: DISCONNECTED, CONNECTED, CONNECTING, DISCONNECTING

Extended values

Assuming you have this folder structure in your application:

├── index.js
└── app
    ├── enums
    │   ├── env.json
    │   └── error-ids.yaml
    └── etc
        ├── database.js
        ├── errors.js
        └── stuff.js

And you want to use all the file of enums folder across your app as plain js objects.

You could do it like this:

In the first lines of index.js (assuming that this is where your app would start):

const vboxPath = require('value-box/path');
vboxPath(__dirname, ['/app/enums']);

Be sure that these two lines are the first thing to be executed in your app setup.

You must send __dirname so that ValueBox can use your app's path instead of its own path.

ValueBox will map the received list of directories and export their paths to an environment variable called VALUE_BOX_PATH.

After you did this setup, every time you require value-box, it will read those folders and map all the valid files it find.

After the extended setup, value-box would give you something like:

{
  //Presets:
  environments: { /* Preset stuff */ },
  http: { /* Preset stuff */ },
  mongooseStatus: { /* Preset stuff */ },

  // Mapped from the files:
  env: { /* File content */ },
  errorIds: { /* File content */ }

}

Follow your innermost convention instinct to get some values.

Or check all the options available:


const vbox = require('value-box');

console.log(vbox);