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

@qa-compass/toolbar

v0.0.23

Published

Add a file into the repo called `.env.local`. It should look like this:

Downloads

800

Readme

Create environment file

Add a file into the repo called .env.local. It should look like this:

VITE_SCRIPT_ID=<your-script-id-comes-here> # you can get this from the dashboard

How to develop on localhost with an iPhone

  • Connect iPhone with cable to Mac
  • On Mac: System Settings -> Sharing -> Internet Sharing
  • In terminal run ifconfig | grep inet and search your ip address e.g. 192.168.0.159
  • vite --host 192.168.0.159
  • Should be openable on Mac and iPhone

TestWebsite

./customer acts as a test website using our the build from ./script. It would be nice to npm run dev in ./customer and ./script for development. However, there are some issues with react-refresh and some with vite, because neither vite nor React expects such a use case.

So for now the idea is to only npm run dev in ./script for development and use instead. Then we can build ./script, copy ./dist to .customer and import it there.

Deployment Checklist

  • z-index sidenav
  • Mobile
  • Placing pin while being scrolled down
  • Pin should stay in same place when scrolling

How to test vite plugin

Bad setup:

  • in vite.config.ts import { qaCompassCodeJumpViteReact } from "./plugin.js";
  • Run npm run build in plugin repo and copy budnle into ./plugin.js

TODO

  • magic report -> change value of input -> click somewhere -> reject(new Error("Failed to load image"));