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

webpack-node-test-runner

v0.0.10

Published

Tool to help running tests with webpack

Downloads

27

Readme

webpack-node-test-runner

Simple CLI that helps run your tests in node after bundling with webpack, and then rerun test files dependent on the files that changed.

setup

  • Use require.context to load your test files from a single entry file

  • Define your node modules as externals

  • Within your entry file, check for the __webpack_ids_to_test__ variable. When using watch, this array will include module ids for the tests that need to be re-run.

    const context = require.context('./', true, /\/__tests__\//)
    if (global.__webpack_ids_to_test__) {
      // only require the necessary components
      global.__webpack_ids_to_test__.forEach(id => __webpack_require__(id))
    } else {
      // require all includes modules
      context.keys().forEach(key => context(key))
    }

run

Once setup use webpack-node-test-runner from the command line:

webpack-node-test-runner --config ./webpack_config/test --watch -- --reporter dot

Use webpack-node-test-runner --help to see all options. Options defined after the -- are sent to mocha, so things like --reporter and --ui should be defined here.

inspiration

This project, especially the feature to only re-run certain tests, was inspired by webpack-mocha. I had intended to add support for devtool: "eval" to that project but found the approach different from what I had in mind, and it was simple enough to re-write.