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

@dimerapp/context

v2.0.0

Published

Context to be passed around dimer low level libraries

Downloads

20

Readme

Dimer Context

Runtime context for dimer

travis-image npm-image

Dimer is a combination of several small modules, joining together to build the final app. Passing user options from top-level to all these libraries can be daunting and hence a context is used to read and write runtime values.

At the lowest level, context starts with the basePath and new values are added, as it is passed through several modules. Also you can debug the actions taken on the context by defining DEBUG environment variable.

DEBUG=dimer:context node yourapp.js

Installation

npm i @dimerapp/context

# Yarn
yarn add @dimerapp/context

Usage

const Context = require('@dimerapp/context')
const ctx = new Context(__dirname)

// later pass around other libs
const config = new (require('@dimerapp/config-parser'))(ctx)
const store = new (require('@dimerapp/datastore'))(ctx)

API

The following methods are available to read/write to the context.

constructor(basePath, [distPath = 'dist'])
const ctx = new Context(__dirname, 'dist')

set(lib, key, value)

The lib option is required for debugging, so that context can log name of the library, which has mutated the state.

ctx.set('config-parser', 'config', value)

get(key)

Get value for a given key. We recommend you not to mutate the return value and instead transform it.

ctx.get('config')

remove(key)

Remove value for a given key

ctx.remove('config')

Change log

The change log can be found in the CHANGELOG.md file.

Contributing

Everyone is welcome to contribute. Please take a moment to review the contributing guidelines.

Authors & License

thetutlage and contributors.

MIT License, see the included MIT file.