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

named-context

v0.1.0

Published

A React context wrapper which lets you get context by name.

Downloads

4

Readme

named-context

named-context is a wrapper for React.createContext, letting you retrieve specific context component pairs by name. It "blackboxes" the singleton nature of createContext so that you can use a single import and a known string name to get the context you want.

Installation and use

Install into your project with npm i named-context (for Node.js), or npm i -D named-context (for Webpack/Parcel/Browserify or other bundled projects).

Basic example

Provider file

import getContext from 'named-context';

const Context = getContext('some identifier');

export default () => (
  <Context.Provider value={{ name: 'James T Kirk' }}>
    <Consumer />
  </Context.Provider>
)

Consumer file

import getContext from 'named-context';

const Context = getContext('some identifier');

export default () => (
  <Context.Consumer>
    {value => (
      <p>Name: {value.name}</p>
    )}
  </Context.Consumer>
)

API

named-context exports a single function as the default export.

getContext

import getContext from 'named-context';

const { Provider, Consumer } = getContext('identifier');

getContext takes a single string argument and returns the object created by React.createContext(). All calls to getContext with the same string argument will return the same context object. You can use getContext() across files.

Usage of Provider and Consumer can be found in the React docs.

ES support

This library is compiled with Babel to support IE11, last 3 Safari, and last 2 Chrome and Firefox. Publically, it expects ES6 methods/objects to exist (natively or polyfilled). Realistically, you could test it and find that it might work in a pure ES5 environment.

If a case is found which doesn't work in pure ES5 environments, and it doesn't require drastic changes or much uglier code, I'll pull those changes in.

Getting help

You can frequently find me (samsch) hanging out in ##javascript, #Node.js, and #reactjs on Freenode, especially during US working hours. This is a small library, so it's likely someone else could help you as well if you point them at the source file and your code.

Contributing

The projects builds with npm run build, which is also called on pre-publish.