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 🙏

© 2026 – Pkg Stats / Ryan Hefner

balar-lint

v0.3.0

Published

TypeScript Language Server plugin that enforces correct usage of balar's batching APIs through static analysis and real-time IDE diagnostics

Readme

Balar TypeScript Language Server Plugin

The balar TypeScript library allows developers to build network-efficient batch processing APIs without the headaches related to the partitioning logic you would need when your items have different processing/data-fetching requirements.

Using this library, some rules need to be enforced to ensure correct batching behavior in certain scenario. Correct usage of certain DSL-like APIs of this library cannot be enforced directly by the library at runtime, much like React hooks. This TypeScript Language Server plugin fills this gap by performing static analysis on your codebase to spot usage issues, displaying real-time diagnostics directly in your IDE with little configuration.

Features

This plugin enforces two key rules for using balar:

  1. No balar-wrapped functions outside balar context: Balar-wrapped functions (functions wrapped with balar.wrap.fns() or balar.wrap.object()) must be called inside a balar.run() context.

  2. No conditional calls inside balar context: Inside balar.run(), balar-wrapped functions must not be called conditionally (e.g., inside if statements, switch statements, ternary operators, or short-circuit operators like && or ||). Use balar.if() or balar.switch() instead.

Installation

  1. Install the plugin in your project:

    npm install --save-dev balar-lint
  2. Configure your tsconfig.json to use the plugin:

    {
      "compilerOptions": {
        "plugins": [
          {
            "name": "balar-lint"
          }
        ]
      }
    }
  3. Restart your TypeScript language server if needed (in VS Code: CMD+Shift+P → "TypeScript: Restart TS Server")

Examples

❌ Error: Calling outside balar.run()

import { balar } from "balar";

const wrap = balar.wrap.fns({
  fetch: async (url: string[]) => {
    return url.map((u) => u + " fetched");
  },
});

// ERROR: Balar-wrapped function must be called inside a balar.run() context
const fetch = wrap.fetch("https://google.com");

✅ Correct: Calling inside balar.run()

const results = await balar.run(urls, async (url) => {
  const data = await wrap.fetch(url);
  return data;
});

❌ Error: Conditional call inside balar.run()

const results = await balar.run(urls, async (url) => {
  let data;

  // ERROR: Balar-wrapped function must not be called conditionally
  if (url.includes("google")) {
    data = await wrap.fetch(url);
  }

  return data;
});

✅ Correct: Using balar.if()

const results = await balar.run(urls, async (url) => {
  const data = await balar.if(
    url.includes("google"),
    async () => await wrap.fetch(url),
    async () => undefined
  );

  return data;
});

Limitations

  • IDE-only diagnostics: This plugin only provides diagnostics in your IDE. It does not block the TypeScript build process (tsc). This is a limitation of TypeScript Language Server plugins.

License

MIT