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-webpack-resolver

v0.3.0

Published

It is a jest plugin for enchanging jest resolving behaviour to webpack resolver through the webpack.config.js

Downloads

49,096

Readme

Jest Webpack Resolver Plugin

It is a jest plugin for enchanging jest resolving behaviour to webpack resolver through any webpack config.

Why?

webpack 2 provides some custom resolving opinions for enchanging resolving behaviours like directory-named-webpack-plugin and you can't match this kind of resolves with jest's default resolver and this plugins completely changing resolving rules.

With webpack resolving you don't have to worry about these resolving options:

resolve.alias
resolve.descriptionFiles
resolve.extensions
resolve.mainFields
resolve.mainFiles
resolve.modules
resolve.plugins

Install

Jest resolver option supported for jest >=20 versions.

install with yarn

yarn add jest-webpack-resolver -D

or install with npm

npm install jest-webpack-resolver -D

add to your jest configuration

{
  "resolver": "jest-webpack-resolver"
}

Configuration

By default plugin tries to detect webpack.config.js. You can configure it from package.json or jest.config.js (or any other jest config file)

add jestWebpackResolver to your package.json file at root level:

{
  "name": "",
  "version": "",
  "jestWebpackResolver": {
    "webpackConfig": "./path/to/webpack.config.js"
  }
}

or at your jest.config.js or jest.config.json file

{
  // ...
  jestWebpackResolver: {
    webpackConfig: './path/to/webpack.config.js'
  }
}

to stop the 'Webpack Resolver using: ./...' message use the silent option

{
  "jestWebpackResolver": {
    "silent": true,
    "webpackConfig": "./path/to/webpack.config.js"
  }
}