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

biome-plugin-no-type-assertion

v1.0.2

Published

A biome plugin that disallows type assertions in TypeScript code.

Readme

biome-plugin-no-type-assertion

A Biome linter plugin that disallows type assertions in TypeScript code, encouraging the use of type guards and proper typing instead.

Installation

Install the plugin as a dev dependency:

npm install --save-dev biome-plugin-no-type-assertion

or with your preferred package manager:

yarn add -D biome-plugin-no-type-assertion
pnpm add -D biome-plugin-no-type-assertion
bun add -D biome-plugin-no-type-assertion

Usage

Add the plugin to your Biome configuration file (biome.json or biome.jsonc):

{
  "$schema": "./node_modules/@biomejs/biome/configuration_schema.json",
  "plugins": ["node_modules/biome-plugin-no-type-assertion/no-type-assertion.grit"]
}

To ignore it

// biome-ignore lint/plugin/no-type-assertion: <reason>
const a = 5 as number;

The plugin will now check your TypeScript code and report errors when it detects type assertions.

What it catches

The plugin detects only one form of type assertions in TypeScript (the most used):

as syntax: expression as Type

const a = 5 as number; // ❌ Error
const b = ["nope"] as string[]; // ❌ Error

Unfortunately, due to limitations in the Grit pattern language, the plugin cannot currently detect type assertions using the angle-bracket syntax. Examples of unsupported cases include:

// These are "uncommon" type assertions that the plugin at the moment cannot catch
const b = <number>5;
console.log(<string>(<unknown>b));

Why avoid type assertions?

Type assertions bypass TypeScript's type checker and can hide potential bugs. Instead, consider:

  • Type guards: Use runtime checks with type predicates
  • Proper typing: Define correct types at the source
  • Type narrowing: Let TypeScript infer types through control flow analysis

Contributing

Contributions are welcome! Here's how to get started:

Setup

  1. Clone the repository:

    git clone https://github.com/albertodeago/biome-plugin-no-type-assertion.git
    cd biome-plugin-no-type-assertion
  2. Install dependencies:

    npm install

Development

The plugin is defined in no-type-assertion.grit using the Grit pattern language.

Testing

Run the test suite:

npm test

Tests are located in the test directory and use Vitest. Test fixtures can be found in test/fixtures.

Publishing

To publish a new version of the plugin:

  1. Update the version in package.json.
  2. Publish to npm:
    npm publish
  3. Tag the release in GitHub creating a Release with the changes.

License

MIT © Alberto De Agostini