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

enum-tool

v2.0.0

Published

a enum tool

Downloads

4

Readme

enum-tool

The purpose of this library is resolving the troubled expressions in actual development.

  • It is bother to manage enum and info that is associated with the enum.
  • No Intelligence in traditional coding.

📕 Older Version Doc

🚀 Features

  • 💪 Type Strong: Written in TypeScript
  • 💡 Code Intelligence: Powered by Typescript

📦 Install

npm i enum-tool

🦄 Full Usage

import { enumify } from 'enum-tool'

// init enum
// tip: you must use `as const` at the end of array.
//      you can also use /** @type {const} */ in javascript develop environment
const SexEnum = enumify([
  { key: 'MALE', value: 'male', meta: { desc: 'male' } },
  { key: 'FEMALE', value: 'female' },
] as const)

// output: 0
// you can get code intelligence here
console.log(SexEnum.MALE)

const maleVo = SexEnum.get(SexEnum.MALE)

// output: male
// you can get code intelligence here
console.log(maleVo.value)

// you can get all enum options by call `getAll` method
const sexList = SexEnum.getAll()

The SexEnum is equivalent to

const SexEnum: {
  MALE: 'male'
  FEMALE: 'female'
}

The enumify is the core function of the library. It accepts the array of enum info as params. In single enum info obj, the key field is matched with the key of SexEnum, the value is matched with the value of SexEnum. You can set custom data in meta field.

Call SexEnum.get method get the single enum info.

Call SexEnum.all method get the all enum info list.

👾 Compare code style with tradition

Not use library

// init enum
const SexEnum = {
  MALE: 'male',
  FEMALE: 'female'
}

// init enum info list
const sexList = [
  { label: 'man', value: SexEnum.MALE },
  { label: 'woman', value: SexEnum.FEMALE },
]

// mock enum value from backend
const unknownSex = 'unknown'

// render info
if (unknownSex === SexEnum.MALE || unknownSex === SexEnum.FEMALE) {
  // tip: there has no code intelligence with maleVo, you can't get female info in coding
  // you need call find method, it is not concision
  const maleVo = sexList.find(item => item.value === unknownSex)
  render(maleVo)
}

Using library

// only init and maintain at here
const SexEnum = enumify([
  { key: 'MALE', value: 'male', meta: { label: 'man' } },
  { key: 'FEMALE', value: 'female', meta: { label: 'woman' } }
] as const)

// mock enum value from backend
const unknownSex = 'unknown'

// render info
if (unknownSex === SexEnum.MALE || unknownSex === SexEnum.FEMALE) {
  // you can get code intelligence here
  const unknownVo = SexEnum.get(unknownSex)
  render(unknownVo)
}