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

@fenge/types

v0.5.0

Published

A type replacement for enhancing TypeScript built-in apis.

Readme

@fenge/types

PRs Welcome

A type replacement for enhancing TypeScript built-in apis.

What is it

TypeScript supports replacing built-in definitions by installing a lib to node_modules, since v4.5. TypeScript built-in definitions have a large number of any, which are not type-safe enough.

This is a library that provides stricter type definitions for enhancing TypeScript built-in apis.

Features

Here are all features and differences between the built-in definitions and this library.

Without this library:

  • 🚨 JSON.parse returns any.
  • 🚨 Array.isArray returns any[].
  • 🚨 new Map() generates Map<any, any>.
  • 🚨 new Promise() can reject a non Error variable.
  • 🚨 Promise.reject accepts any as a reason.
  • 🚨 Promise.prototype.catch accepts (reason: any) => void | PromiseLike<void>.
  • 🚨 Promise.prototype.then accepts (reason: any) => void | PromiseLike<void> for the second parameter.

With this library:

  • 👍 JSON.parse returns unknown.
  • 👍 Array.isArray returns unknown[].
  • 👍 new Map() generates Map<unknown, unknown>.
  • 👍 new Promise() must reject an Error variable.
  • 👍 Promise.reject accepts Error as a reason.
  • 👍 Promise.prototype.catch accepts (reason: unknown) => void | PromiseLike<void>.
  • 👍 Promise.prototype.then accepts (reason: unknown) => void | PromiseLike<void> for the second parameter.

Usage

Firstly, if you have install @types/node, make sure its version >= 18.0.0.

Then, add this library to devDependencies field in package.json file. You can replace the version of 0.4.0 with the expected version.

{
  "devDependencies": {
    "@typescript/lib-es2020": "npm:@fenge/[email protected]"
  }
}

Finally, run npm install or yarn install or pnpm install.

After that, writing TypeScript code will be more type-safe. Example:

const foo = JSON.parse('{"bar": 1}'); // The `foo` is `unknown` type now.
console.log(foo.baz + 1); // error: 'foo' is of type 'unknown'.

License

MIT