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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@scripthungry/better-switch

v1.0.15

Published

A simple alternative to the switch statement for matching strings and returning values

Readme

RelativeCI

@scripthungry/better-switch

A simple alternative to the switch statement for matching strings and returning values

To install and use

npm i @scripthungry/better-switch

In your code:

import betterSwitch from '@scripthungry/better-switch'

Examples

Javascript:

Simple example:

const returnVal = betterSwitch('test', {
  test: () => 'test value', 
  default: () => 'default value' 
}) // returnVal === 'test value'

Non-existent key returns default key value:

const returnVal2 = betterSwitch('non existent key', { 
  test: () => 'test value', 
  default: () => true 
}) // returnVal2 === true

Error due to non existent key and no default key:

const returnVal3 = betterSwitch('non existent key', { 
  test: () => 'test value', 
  test2: 'test2 value' 
})

Typescript:

Enforcing a consistent return type using type inference from the first return value:

const returnVal = betterSwitch('test', { 
  test: () => 'test value', 
  default: () => 'default value' 
}) // returnVal === 'test value'

Enforcing a specified consistent return type:

const returnVal = betterSwitch<string>('test', { 
  test: () => 'test value', 
  default: () => 'default value' 
}) // returnVal === 'test value'

Typescript error because the default key does not return the same type as the first key:

const returnVal = betterSwitch('test', { 
  test: () => 'test value', 
  default: () => true 
})

Allowing unknown return types:

const returnVal = betterSwitch<unknown>('non existent key', {
  test: () => 'test value', 
  default: () => true 
}) // returnVal === true

Allowing multiple specified return types

const returnVal = betterSwitch<string | boolean>('non existent key', { 
  test: () => 'test value', 
  default: () => true 
}) // returnVal === true