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

oxlint-comments

v1.0.0

Published

Oxlint plugin that requires // line comments instead of /* */ or JSDoc.

Readme

oxlint-comments

Oxlint plugin that requires // line comments.

// hello world

Block comments and JSDoc are reported, and standalone comments can be rewritten automatically:

/* hello world */
/** Adds two numbers. */
// hello world
// Adds two numbers.

The rule is written with Oxlint's createOnce plugin API.

Install

pnpm add -D oxlint-comments

Usage

.oxlintrc.json:

{
  "jsPlugins": ["oxlint-comments"],
  "rules": {
    "oxlint-comments/no-block-comments": "error"
  }
}

Or oxlint.config.ts:

import { defineConfig } from 'oxlint'

export default defineConfig({
  jsPlugins: ['oxlint-comments'],
  rules: {
    'oxlint-comments/no-block-comments': 'error',
  },
})

Rule: no-block-comments

Reports every /* */ block comment and every JSDoc /** */ comment.

Allowed by default:

  • // line comments
  • shebangs (#!/usr/bin/env node)
  • JSX empty-expression comments ({/* ... */}), because // is not valid there
  • linter and coverage directives such as /* oxlint-disable */ and /* eslint-disable */
  • compiler and bundler annotations such as /* #__PURE__ */ and /* webpackChunkName: "mod" */

Standalone block comments are autofixed to // lines. Inline comments such as fn(/* hint */ value) are reported without a fix, because rewriting them would break the surrounding code.

Options

{
  "oxlint-comments/no-block-comments": [
    "error",
    {
      "allowDirectives": true,
      "allowAnnotations": true,
      "ignorePattern": "^\\s*TODO\\b"
    }
  ]
}

| Option | Default | Meaning | | ------------------ | ------- | ------------------------------------------------------------------------------- | | allowDirectives | true | Allow Oxlint, ESLint, Prettier, Istanbul, c8, and similar directive comments. | | allowAnnotations | true | Allow bundler and minifier annotations that have to stay block comments. | | ignorePattern | unset | Skip block comments whose body matches this regular expression. |

Set allowDirectives or allowAnnotations to false if you want those comments converted to // as well.

Development

pnpm test
pnpm lint
pnpm fmt

pnpm build bundles the plugin with tsdown. pnpm lint runs Oxlint and oxfmt --check.

License

MIT