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 🙏

© 2025 – Pkg Stats / Ryan Hefner

hello_jest

v1.0.0

Published

Example npm module using jest for testing.

Downloads

7

Readme

hello_jest A hello world example of testing javascript using Jest

Build Status Coverage Status

This repository is intended to provide a relatively simple and minimal example of Javascript testing and code coverage for a client side Javascript module, specifically for jQuery plugins.

I hope people (like me) find it helpful when they want to create npm modules with automated testing and coverage reports.

To enable continuous integration and code coverage evaluation I registered this repository with the Travis CI service and the coveralls coverage service.

What are the files?

Here are the files used in the package In some cases they are copied from other places and I don't understand fully their significance, but I needed them to get everything working.

hello_jest/src/my_plugin.js

This is a silly jQuery plugin implementation which is supposed to represent the main logic of the module that we want to test and publish.

hello_jest/src/index.js

This is the module index file used by npm for creating the module package. It lists everything which should be included in the module.

hello_jest/package.json

This is the npm package description for the module. It describes how to build, test, and package the module and the module top level dependencies and so forth.

hello_jest/jest.config.js

This is the jest configuration file. It describes the test environment (such as environment globals) and where to put the coverage report, among other things.

hello_jest/.travis.yml

This file tells the Travis continuous integration service how to run the tests and register the coverage report.

hello_jest/.babelrc

This file tells the babel preprocessor how to translate javascript.

Background

This repository is built

Eventually

I wanted to add

But I'm giving up on that for now. Maybe later I will return.

References

Setting up jest with puppeteer example:

  374  git clone https://github.com/xfumihiro/jest-puppeteer-example.git
  376  cd jest-puppeteer-example/
  377  node install
  382  npm install yarn -g
  384  yarn add jest-puppeteer
  390  npm install jest -g
  391  jest