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

insighter-bug

v1.12.14

Published

To run the tests, follow these detailed steps:

Downloads

1,633

Readme

Running Tests

To run the tests, follow these detailed steps:

  1. Navigate to the Node Modules Directory: Go to C:\Users\vincm\AppData\Roaming\npm\node_modules and delete the reference to the library. This ensures that any previous versions of the library do not interfere with the tests.

  2. Unlink the Library from the Test Repository: In your test repository, unlink the library to remove any existing connections. This can typically be done using the following command:

    npm unlink your-library-name
  3. Link the Library Locally: Return to the directory where your library is located and run the following command to link it locally:

    npm link

    This command creates a symbolic link from the globally-installed library to your local project.

  4. Link the Library to the Test Repository: Finally, link the library to your test repository by navigating to the test repository and running:

    npm link your-library-name

    This step ensures that your test repository uses the local version of the library for testing.

By following these steps, you can ensure that your tests run against the most current version of your library.

Linking

To run the tests, follow these steps:

  1. Remove Existing Library Reference: Navigate to C:\Users\vincm\AppData\Roaming\npm\node_modules and delete any existing reference to the library to avoid conflicts.

  2. Unlink the Library: In your test repository, unlink the library using:

    npm unlink your-library-name
  3. Link the Library Locally: Go to your library's directory and run:

    npm link

    This creates a symbolic link from the globally-installed library to your local project.

  4. Link the Library to the Test Repository: In your test repository, run:

    npm link your-library-name

    This ensures the test repository uses the local version of the library.

By following these steps, your tests will run against the latest version of your library.

Overview

This project contains action definitions, a Puppeteer builder, and a final player. The player utilizes Puppeteer, which is an optional dependency. Therefore, extensions and online websites must install this library with the --ignore-optional flag for Yarn or the --no-optional flag for npm.

Installation

To install the library globally, including optional dependencies, use the following commands:

For npm:

npm install -g your-library-name --no-optional

For Yarn:

yarn global add your-library-name --ignore-optional

Usage

Once the library is installed globally, you can use the insighter command. Note that the insighter command requires the Puppeteer dependency, so it must be installed with optional dependencies included.

insighter

Make sure to follow the installation instructions to ensure all necessary dependencies are included.