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

perfecttense-editor-staging

v2.6.7

Published

Instant grammar corrections using PerfectTense on any editable on the web.

Readme

Perfect Tense Editor

Browser Extension

Requirements for Extension:

How to run:

In terminal or command prompt

install dependencies
 - npm install
Transpile the code
 - npm run build:extension (transpiles the code)


yarn commands will work too if yarn is installed.

In Chrome web browser

  1. Go to: chrome://extensions
  2. Toggle: "developer mode" on.
  3. Click on: "Load unpacked"
  4. Select the newly created folder "build" from the project folder.
  5. Thats it.

In Firefox web browser

  1. Go to: about:debugging
  2. Select: "Enable add-on debugging"
  3. Click on: "Load Temporary Add-on…"
  4. Open the newly created folder "build" from the project folder, and choose the "manifest.json" file.
  5. Thats it.

Storybook

We have now storybook enabled in out project. This means that you can modify the design of all our components for experimentation or more. You don't need to know any Javascript knowledge to acheieve this.

How to run:

Start Storybook in Terminal

# install dependencies
 - npm install
# start storybook
 - npm run storybook

yarn commands will work too if yarn is installed.

Once it builds, it will load storybook in your default browser with all components we have. To interact with components, change css files of corresponding component located in src/styles, changes will be reflected instantaneously on the opened browser window. This is a good place to mock out new design.

End-to-end tests

Running E2E tests on our test page

  • kill any other local server using port 3080
  • start the mock server: yarn mock-server
  • start webpack for our test page: yarn dev
  • start cypress:
    • to open in Chrome: yarn e2e
    • to run in headless Electron: yarn e2e:ci

Running E2E tests on other websites

  • kill any other local server using port 3080
  • start the mock server: yarn mock-server
  • start webpack for the extension: yarn dev:cypress
  • start cypress with the Chrome extension: yarn e2e:extension