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

babel-plugin-fix-jsdoc

v1.0.2

Published

Always treat JSDoc block comments as leading, not trailing.

Downloads

8

Readme

babel-plugin-fix-jsdoc

yarn add -D babel-plugin-fix-jsdoc
npm install --save-dev babel-plugin-fix-jsdoc

Babel's parser attaches comments as leading and trailing to nodes. This means that when a new node is injected by a transform, there's a risk that a JSDoc block comment that was meant to be leading, will be printed as trailing to the node after which the injection happened, seprating documentation from declaration. This can lead to serious bugs, for example:

import { useMemo } from 'preact/hooks';

/**
 * A component exported as default feature.
 * @param {object} params
 * @param {string} params.suffix
 */
import { jsxs as _jsxs } from "react/jsx-runtime"; // ⬅ BREAKS JSDOC!!!
export default function Component({
  suffix
}) {
  return /*#__PURE__*/_jsxs("div", {
    children: ["example", suffix ? /*#__PURE__*/_jsxs("span", {
      children: ["-", suffix]
    }) : null]
  });
}

This very simply transform iterates through comments of each node in the program, and makes sure that block comments are always recorded as leading.

Installation

Always include this as the first plugin in the list of plugins:

{
 "plugins": [
  "fix-jsdoc",
  [
   "@babel/plugin-transform-react-jsx",
   {
    "runtime": "automatic"
   }
  ]
 ]
}