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

@bytesoftio/tag

v1.0.2

Published

## Installation

Downloads

5

Readme

@bytesoftio/tag

Installation

yarn add @bytesoftio/tag or npm install @bytesoftio/tag

Table of contents

Description

Tags or Branding is a common practice in advanced TypeScript project setups. The main purpose of this approach is to make certain primitive types more predictable.

Let's have a look at this example below:

type UUID = string

type User = {
  id: UUID
}

In this example we have created a type alias UUID that is used on the type User. At the moment, any string value is a valid uuid. For example:

const user: User = { id: "some-uuid" }

This is very implicit and is not very safe since any string fulfills the constraints of the UUID type. What if could make this more explicit?

import { Tag } from "@bytesoftio/tag"

type UUID = Tag<string, "uuid">

type User = {
    id: UUID
} 

// this will not work, string is not assignable to `UUID`
const user1: User = { id: "some-uuid" }

// exlicitly cast it to `UUID` -> you know what you're ding
const user2: User = { id: "some-uuid" as UUID } 

Now you cannot simply assign a string to UUID, this has to be done explicitly.

You can go further and add some type guards, a factory function, etc. for tagged types, but this is not covered here.