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

egg-enums

v1.0.7

Published

Enums for Egg.js

Downloads

15

Readme

egg-enums

NPM version build status Test coverage David deps Known Vulnerabilities npm download

Install

$ npm i egg-enums --save

Usage

// {app_root}/config/plugin.js
exports.enums = {
  enable: true,
  package: 'egg-enums',
};

Configuration

If you're using typescript, add import 'egg-enums'; to your index.d.ts ( go to egg document to get more information ).

In javascript there is NOTHING need to be config.

Example

// {app_root}/app/enums/letters.js
// use array to init enum
// each item's index can be used to find the item
module.exports = app => app.Enum([
  'A',
  'B',
  'C'
]);

// or

// {app_root}/app/enums/colors.js
// use object to set the values
// item can be an object, but MUST have an `id` field at the top level
module.exports = app => app.Enum({
  RED: 1,
  GREEN: 4,
  BLUE: {
    id: 5,
    name: 'blue',
    // other...
  },
});

// then you can use like this
console.log(app.enums.Letters.B === 1);       // true
console.log(app.enums.Letters[2] === 'C');    // true

console.log(app.enums.Colors.GREEN === 4);    // true
console.log(app.enums.Colors[5].name === 'blue');    // true

You can get all keys by use .$keys to get all enums.

// app.enums.Letters.$keys
[
  {
    "id": 0,
    "key": "A"
  },
  {
    "id": 1,
    "key": "B"
  },
  {
    "id": 2,
    "key": "C"
  }
]

// app.enums.Colors.$keys
[
  {
    "id": 1,
    "key": "RED"
  },
  {
    "id": 4,
    "key": "GREEN"
  },
  {
    "id": 5,
    "key": "BLUE",
    "name": "blue"
  }
]

So make sure that DO NOT use $keys to named an enum or use field key in enum items top level when you config.

Questions & Suggestions

Please open an issue here.

License

MIT