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

@pallad/type-check

v1.2.0

Published

Simple type-check utility for libraries authors to prevent issues with type check of objects coming from duplicated module definitions

Downloads

810

Readme


CircleCI npm version Coverage Status License: MIT

Example code

Problem

Sometimes instanceof might not be enough when working on a library that may potentially be installed multiple times in a project. More on that on my blog.

Solution

As described on my blog - using special @type property to indicate final type of an object.

@pallad/type-check is a tool that helps to achieve it in easy way.

Community

Join our discord server

Installation

npm install @pallad/type-check

Usage

Usage with TypeCheck instance in private scope.


import {TypeCheck} from '@pallad/type-check';

// Create TypeCheck instance with globally unique identifier for class

const CHECK = new TypeCheck<SomeLibraryClass>('some-library-class-unique-identifier')

export class SomeLibraryClass {
	constructor() {
		// assign necessary properties to current instance
		CHECK.assign(this);
	}

	static isType = CHECK.isType
}


SomeLibraryClass.isType(new SomeLibraryClass()); // true

Usage with TypeCheck.clazz.

import {TypeCheck} from '@pallad/type-check';

const CHECK = new TypeCheck<SomeLibraryClass>('some-library-class-unique-identifier')

export class SomeLibraryClass extends CHECK.clazz {
	// properties assignment are done in constructor automatically
	// static `isType` method is also assigned
}

SomeLibraryClass.isType(new SomeLibraryClass()); // true

About type identifiers

Type identifiers (provided in TypeCheck's constructor) must be globally unique so there is no potential conflict with other type check from other libraries. Therefore recommended pattern fo identifier is: [packageName]/[className] For example:

  • @pallad/type-check/SomeClassName
  • @pallad/secret/Secret

Typescript

Obviously everything is properly typed and proper type guards are applied

const CHECK = new TypeCheck<Foo>('foo')

export class Foo extends CHECK.clazz {
	prineMe() {
		return 'hello';
	}
}

if (Foo.isType(value)) {
	// at this stage Typescript knows that `value` is a type of `Foo`
	value.printMe();
}

Multiple types

Object can can hold multiple types for flexibility purposes.

const CHECK1 = new TypeCheck('foo')
const CHECK2 = new TypeCheck('bar')

const value = {};
CHECK1.assign(value);
CHECK2.assign(value);

CHECK1.isType(value); // true
CHECK2.isType(value); // true