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

tdd-webpack-plugin

v0.1.0

Published

run minimal set of unit tests on build under webpack watch

Downloads

4

Readme

tdd-webpack-plugin

Introduction

This plugin assume your project is built on the following structure.

    - yourProjectRoot/
      - src/
        - index.js
        - modules/
          - someModule/
            - test/
            - components/
              - index.js
      - test

It will help you, once changed src/modules/someModule/index.js, runs all the tests under the same parent tree, i.e. src/modules/someModule/test

Installation

    $ npm install --save-dev tdd-webpack-plugin

In webpack config file, extend the TestDrivenDevPlugin class, provide a test function.

The test function is call when webpack emit assets (https://webpack.js.org/api/compiler-hooks/#emit).

The following is the implementation of tdd webpack plugin integrated with cypress (https://www.cypress.io/)

    webpack.dev.conf.js
    
    const tdd = require('tdd-webpack-plugin')
    const cypress = require('cypress')
    
    class CypressTDDPlugin extends tdd.TestDrivenDevPlugin {
      test(specs) {
        // specs is an iterator
        // options accessible through this.options
        let specString = [...specs].join(',')
        if (!specString) {
          specString = `**/${this.options.matchSpecs}`
        }
        cypress.run({
          reporter: 'min',
          config: {
            baseUrl: this.options.baseUrl,
            chromeWebSecurity: false,
            video: false,
            modifyObstructiveCode: false
          },
          spec: specString
        })
      }
    }

Under plugins options, add the instance

    plugins: [
      ........
      new CypressTDDPlugin({
        base: resolve('./src'),
        baseUrl: 'http://localhost:8080',
        testFolder: 'test',
        matchSpecs: '*.spec.js'
      })
    ]

Configuration

Under the Hood

The plugin hooks webpack's emit event (https://webpack.js.org/api/compiler-hooks/#emit), and tracks the changes of the files currently watched by webpack. For each changed source file, it will then traverse upward and find the first test folder, and run all the specs under that folder.