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

@biscuit-auth/web-components

v0.7.0

Published

This repo is part of the [eclipse biscuit](https://github.com/biscuit-auth/biscuit) project.

Readme

biscuit-web-components

This repo is part of the eclipse biscuit project.

Biscuit web components are tools used to provide in-browser biscuit tooling. See documentation

How to update tree-sitter

Tree-sitter is packaged in a way that makes it difficult to load it up with wds, it is packaged as a CommonJS module (modifying a module.exports object) and as such does not play well with es modules.

The simplest solution I have found is to turn the CommonJS module into an ES module by adding the following at the end of the file:

await TreeSitter.init({
  locateFile(scriptName, scriptDirectory) {
    return "/assets/tree-sitter.wasm";
  }
});
export const Parser = TreeSitter;

This also calls init once, with the proper location of the wasm file.

So to update tree-sitter:

  • run npm install --no-save web-tree-sitter (check if that’s the correct version)
  • cp node_modules/web-tree-sitter/tree-sitter.wasm assets/
  • cp node_modules/web-tree-sitter/tree-sitter-web.d.ts ./tree-sitter.d.ts
  • edit tree-sitter.d.ts
    • remove the declare module scope
    • remove the export = Parser
    • add export in front of class Parser
    • add export in front of namespace Parser
  • cp node_modules/web-tree-sitter/tree-sitter.js ./

cat << 'EOF' >> tree-sitter.js await TreeSitter.init({ locateFile(scriptName, scriptDirectory) { return "/assets/tree-sitter.wasm"; } }); export const Parser = TreeSitter; EOF