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

chrome-tools

v1.1.18

Published

CLI & Node.js library for chrome

Readme

chrome-tools

CLI & Node.js library for Chrome browser data, including passwords, bookmarks, history, cookies, and localStorage.

Requirements

Node.js >= 22.16.0. Chrome's stores are read through the built-in node:sqlite module rather than a native dependency, so there is nothing to compile at install time. 22.16.0 is the floor because that is the release where the connection timeout option began to be honoured — on 22.15 and earlier it is accepted and silently ignored, which is worse than rejected.

The experimental warning

Node prints this to stderr on the first node:sqlite load, once per process:

(node:12345) ExperimentalWarning: SQLite is an experimental feature and might change at any time

Measured across releases, it is emitted on 22.16 through 25.6, and is silent from 25.7.0, where node:sqlite moved to Node's "release candidate" stability index. So on current LTS you should expect to see it.

It is a warning, not an error: stdout stays clean, so piping JSON out of the CLI is unaffected. If you drive this from a harness that treats any stderr output as failure, set NODE_NO_WARNINGS=1 (or run node with --no-warnings) in that harness. This package deliberately does not suppress the warning for you — a library silencing process-wide warnings would hide unrelated ones too.

Because the module is still pre-stable, its API may change between major Node releases. The surface used here — prepare, all, run, close, setReadBigInts, and VACUUM INTO — has been present since 22.5.0.