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

@qiskit/mdx-link-extract

v1.2.0

Published

Fast link extraction in MDX files.

Readme

mdx-link-extract

Fast link extraction in MDX files. This package was created specifically for Qiskit/documentation.

Installation

After the first release of the package, you should be able to install it like any other npm package:

npm install @qiskit/mdx-link-extract
# or
yarn add @qiskit/mdx-link-extract

Developing

Test locally

  • nvm use 22.21.1
  • yarn install
  • yarn build
  • yarn test

You should see all the tests pass.

Publishing

Our GitHub Action prebuilds a binary for each supported platform. We release different npm packages for each platform and add them to optionalDependencies before releasing the major package to npm. The package manager will choose which native package to download from the registry automatically.

Release package

The process isn't ideal for our workflow, we inherited it from the napi-rs template. The release action looks for a new commit on main that starts with a valid semver number (such as 4.12.3). Since we only allow merge commits, this means we need to merge a PR with the semver as a title. We also need to update the package.json in the same PR.

Follow these steps for a foolproof way to make a new release:

  1. Make a new branch from up-to-date main.

    git switch -c release && git reset --hard origin/main && git pull origin main
  2. Run the following command to update package.json and make a commit:

    npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease [--preid=<prerelease-id>] | from-git]
  3. Run gh pr create and accept the defaults. This will create a PR with the correct title. Submit the PR.

  4. Once CI has passed and been approved, merge the PR. This will trigger a release.

WARN: Don't run npm publish manually.