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

unreachable-ts

v2.0.0-alpha.1

Published

Simple function to do a compile-time check for unreachability and to throw the prescribed runtime error is it is bypassed.

Downloads

381

Readme

unreachable-ts

This is a small one-liner function for marking the unreachable code which can be checked to be unreachable at type-level.

Examples

The main example use-case is an exhaustive switch-case statement, like this:

type Union = 'First' | 'Second';
declare function getValue(): Union;

import { unreachable } from 'unreachable-ts';

const value: Union = getValue();
switch (value) {
  case 'First':
    // do something
    break;
  case 'Second':
    // do something else
    break;
  default:
    unreachable(value, new Error("Value must be either First or Second"));
}

If the getValue function returns any value not corresponding to the declared type, it will fall into the default branch and throw a runtime error.

On the other hand, if the Union type is changed but the switch/case is not, TypeScript will throw a compilation error:

type Union = 'First' | 'Second' | 'Third';
declare function getValue(): Union;

import { unreachable } from 'unreachable-ts';

const value: Union = getValue();
switch (value) {
  case 'First':
    // do something
    break;
  case 'Second':
    // do something else
    break;
  default:
    // Error: TS2345: Argument of type 'Error' is not assignable to parameter of type 'never'.
    unreachable(value, new Error("Value must be either First or Second"));
}

Why making a package for this?! It's overkill!

Well, it's mainly for the sake of removing repetition. It's better to have one import in several places than to duplicate that code, don't you think so? And anyway, if you feel like you don't want to pull a whole project for a small one-liner, you are free to just copy the contents to you - it's in public domain, anyway.

Isn't there an unreachable package already?

Well, there is... but you know, every programmer has to reinvent the wheel sometimes, right?

Why your package is better that that?

Just because of license (the Unlicense), probably. Nothing more. It's just too simple to be done wrong.

I'd like to add some more functionality for my use case...

Just don't forget that this is public domain, and, if I ever get any pull request - this request's contents will be considered public domain too.

Why only TypeScript? What about Flow?

It seems that TypeScript has won anyway. And, to be honest, I never worked with Flow, so... how can I compete on this field?