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

jest-setup-glob

v1.0.0

Published

Apply different Jest setup files based on the test's filename.

Downloads

5

Readme

jest-setup-glob

Apply different Jest setup files based on the test's filename.

Motivation

Let's say you've got two groups of tests: unit tests running in Node.js and integration tests that run in an automated browser (i.e. Chromium). Each of those test groups has its own environment, which you declare in the respective setup files with Jest.

Usually, to provision such setup, you create two separate Jest setup files, but because Jest executes all setup files you provide in the setupFilesAfterEnv configuration option, you introduce two separate commands to run your tests just for the sake of using a different configuration in order to use a different setup file:

{
  "scripts": {
    "test:unit": "jest",
    "test:e2e": "jest --config jest.e2e.config.js"
  }
}

This package allows you to run a single jest command with a single configuration file and get different environments bootstrapped based on the test's filename.

Usage

$ npm install jest-setup-glob

Create/edit the jest.setup.js file:

// jest.setup.js
const setup = require('jest-setup-glob')

setup({
  '**.browser.test.js': './jest.setup.browser.js',
  '**.test.js': './jest.setup.node.js',
})

This library uses macromatch string matcher. Refer to its documentation to write a valid glob pattern.

Reference the jest.setup.js file in your jest.config.js:

// jest.config.js
module.exports = {
  setupFilesAfterEnv: ['./jest.setup.js'],
}
$ jest myTest.test.js
# using "jest.setup.js"...

$ jest browserCache.browser.test.js
# using "jest.setup.browser.js"...