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

extension-from-store

v0.1.1

Published

Download public browser extensions from official stores

Downloads

222

Readme

Download public browser extensions from official stores

extension-from-store Version Downloads workflow

  • Chrome Web Store, Microsoft Edge Add-ons, Firefox AMO
  • Easy-to-use API
  • Node.js + CLI support

Install

npm i extension-from-store

Usage

Designed for quiet reliability, extension-from-store keeps the interface simple and the output predictable.

Via Node.js:

import {fetchExtensionFromStore} from 'extension-from-store'

const url =
  'https://chromewebstore.google.com/detail/adblock-plus-free-ad-bloc/cfhdojbkjhnklbpkdaibdccddilifddb'

const options = {
  outDir: './extensions',
  userAgent: 'my-tool/1.0.0',
  extract: true,
  logger: {
    onInfo: (message) => console.log(message),
    onWarn: (message) => console.warn(message),
    onError: (message, error) => console.error(message, error)
  }
}

await fetchExtensionFromStore(url, options)

Via CLI (default command is fetch):

npx extension-from-store --url "<store-item-url>"
npx extension-from-store --url "<store-item-url>" --out ./my-exts
npx extension-from-store --url "<store-item-url>" --version 2.1.0 --extract
npx extension-from-store --url "<store-item-url>" --extract

The store is detected from the URL.

Output

<out>/
  <identifier>@<resolved-version>/
    extension.meta.json
    ...

If the target folder already exists, the operation fails.

By default, extension-from-store downloads the archive without extraction. When you pass --extract, it unpacks the archive and writes metadata.

When extraction is disabled, the archive is saved as:

<out>/<identifier>[@<version>].crx
<out>/<identifier>[@<version>].xpi

Extraction Rules

  • .crx: strip CRX header, extract ZIP payload
  • .xpi: treat as ZIP
  • No normalization, no rewriting, no formatting

extension.meta.json

{
  "store": "chrome | edge | firefox",
  "identifier": "<identifier derived from the URL>",
  "version": "<resolved version>",
  "manifestVersion": 2 | 3
}

This file is written by extension-from-store to the same folder as the extracted files.

CLI Flags

| Flag | Required | Description | | --- | --- | --- | | --url <string> | Yes | Extension URL | | --out <path> | No | Output directory (default: ./extensions) | | --version <string> | No | Version hint | | --user-agent <string> | No | Override user agent | | --extract | No | Extract after download (default: download only) | | --quiet | No | Suppress info logs | | --verbose | No | Emit verbose info logs | | --json | No | JSON lines output to stdout |

Logging

Library logging is opt-in via the logger hooks. The library never writes directly to stdout/stderr.

Exit Codes

  • 0 success
  • 1 invalid input
  • 2 unsupported store
  • 3 not found / not public
  • 4 download failed
  • 5 extraction failed
  • 6 filesystem conflict
  • 7 store incompatibility

License

MIT (c) Cezar Augusto.