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 🙏

© 2024 – Pkg Stats / Ryan Hefner

pchrome

v1.0.4

Published

Promisified Chrome APIs with type declarations.

Downloads

5

Readme

pchrome

I wanted TypeScript type declarations and a Promise-oriented API for the Chrome API.

You can get one of the two, but not both, with existing stuff:

It's unfortunate, because the Chrome API is big (so you want type support) and does a lot of async I/O (so you want Promises and async/await).

Usage

index.js and index.d.ts are generated files that are in the repo and should work out of the box if you just npm install --save pchrome.

Then import * as pchrome from 'pchrome'; or var pchrome = require('pchrome') as appropriate for your module system.

Now use pchrome as though it's the chrome object, except calls with a callback parameter now return a Promise instead. (Look at the type declarations in index.d.ts for more details.) All other calls, events, member variables, and so on are still present on pchrome as well.

Read on for how the index.js and index.d.ts generated and how you can regenerate them.

Generation

See generate.ts, which has a little TypeScript d.ts grammar and basically transforms DefinitelyTyped's d.ts file into a promiseful version, along with JS wrappers for all the async functions.

Regeneration

Install dependencies with npm install and typings install.

Now npm -g install ts-node.

Then run npm run build, which executes generate.ts. That produces index.js and index.d.ts which are the promisified Chrome APIs.

Example

There's an example Chrome extension in the example/ subfolder.

Run webpack in that folder (assuming you have webpack and TypeScript installed). It will generate the bundle.js for the Chrome extension from background.ts and the pchrome library in the parent folder.

Then load example/ into Chrome as an unpacked extension.