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

@commandbar/foobar

v0.5.75

Published

## Usage

Downloads

3,790

Readme

@commandbar/foobar

Usage

npm install @commandbar/foobar

or

yarn add @commandbar/foobar

First initialize CommandBar and then boot it up!

// App.js

import { init as initCommandBar } from '@commandbar/foobar';

initCommandBar('MY_ORG_ID');

// Identify user...
const userID = ...

window.CommandBar.boot(userID);

Run Tests as in CI

Tests in CI run in a linux container, to run these locally run:

yarn playwright:linux

After this, you'll have a full linux environment that can be used to run CI-like tests locally with yarn playwright test for example.

Regenerate Screenshots

To regenerate the screenshots for local runs, you just need to run the commands with -u at the end, like yarn test-storybook -u or yarn playwright test -u.

To regenerate screenshots for CI, you need to have docker installed. After this, you're able to recreate the screenshots:

Component Tests

yarn test-storybook:regenerate

Integration Tests

yarn playwright:regenerate

Customer Tests

yarn playwright:e2e:regenerate

Bear in mind that the commands above may break your node_modules installation, because they're mounting it in a linux container. Running yarn after the screenshots have been updated will sort it out.