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

edata-store

v1.1.5

Published

build global store and get namespaced edata

Downloads

3

Readme

edata-store

Easily use global store with edata.

Build Status NPM Version

Install

You can install from NPM.

npm install --save edata-store

Usage

  1. Initialize store using initStore (normally at your entry file)
import {initStore} from 'edata-store'
initStore() // `'default'` namespace
// OR
initStore(`xx_space`)
  1. call getStore(), and you get an edata instance. (normally at your component file)
// any where in your source
import {getStore} from 'edata-store'
getStore().set('xx', 1)  // `'default'` namespace
getStore().get('xx').toJSON() // 1

Or pass the namespace arg:

getStore('xx_space').set('xx', 2)  // `'xx_space'` namespace
getStore('xx_space').get('xx').toJSON() // 2

Above create a separate edata under xx_space namespace.

API

The typescript definition as below:

/**
 * Initialize store for namespace, after that you can call getStore
 * @param namespace {string} The namespace of cacheStore, empty for 'default'
 * @param initData {any} The edata initData
 * @param edataOptions {IOptions} The edata Initialize IOptions
 * @returns {edataRoot} The edata root instance
 */
export declare function initStore(namespace?: string, initData?: any, edataOptions?: Partial<IOptions>): edataRoot;
/**
 * Get store using namespace from cacheStore
 * @param namespace {string} The namespace of cacheStore, empty for 'default'
 * @returns {edataRoot} The edata root instance
 */
export declare function getStore(namespace?: string): edataRoot;