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

@wext/tabs

v0.1.4

Published

Web Extensions polyfill for the `browser.tabs.*` API.

Readme

Web Extensions polyfill: tabs

Web Extensions polyfill for the browser.tabs.* API.

The goal with this package is to implmenet a subset of the Web Extensions API that works for Chrome, Firefox, Safari and Edge.

Since this is a subset of the Web Extensions API, not all properties will be abailable. The best way right now is to look in the index.d.ts which holds TypeScript definitions of the properties available. The interface specificed in the TypeScript definitions should work on all platforms.

PRs welcome 🚀

Installation

npm install --save @wext/tabs

Usage

const tabs = require('@wext/tabs')

tabs.create({ active: true, url: 'https://google.com' }).then((tab) => {
  // A tab with google is now open and focused
})

Implemented methods

| Feature | Chrome | Firefox | Safari | Edge | | ------- | :----: | :-----: | :----: | :--: | | create | ✅ | ✅ | ✅ | ❌ | | executeScript | ✅ | ✅ | 🐝 | ❌ | | remove | ✅ | ✅ | ✅ | ❌ | | update | ✅ | ✅ | ✅ | ❌ | | query | ✅ | ✅ | ✅ | ❌ |

Implemented events

| Feature | Chrome | Firefox | Safari | Edge | | ------- | :----: | :-----: | :----: | :--: | | onUpdated | ✅ | ✅ | 🐝 | ❌ |

🐝 Safari support

Since Safari has a significantly different API than all other browsers, some APIs are only implemented as closely as possible.

A small shim is required to be loaded for the following functionality to work properly:

| Feature | Part | | ------- | ---- | | executeScript | Entire API | | onUpdated | Updates to the status property |

The shim needs to be loaded on every site that you intend to use any of the mentioned APIs. This means that you need to request the <all_urls> permission to run executeScript on the currently focused page, something that isn't needed in the other browsers.

The source is in the file safari-shim.js, it should be loaded as a content script that runs at the start of every page.

Here is an example on how to include it with WebPack:

const CopyWebpackPlugin = require('copy-webpack-plugin')
const WextManifestWebpackPlugin = require('@wext/manifest/webpack')

// ...

module.exports = {
  // ...

  plugins: [
    new CopyWebpackPlugin([
      { from: require.resolve('@wext/tabs/safari-shim'), to: 'safari-shim.js' }
    ]),

    new WextManifestWebpackPlugin('safari', {
      // ...

      content_scripts: [{
        matches: ['*://*/*'],
        run_at: 'document_start',
        js: ['safari-shim.js']
      }]
    })
  ]
}