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

@trellisorg/nx-jest

v0.0.6

Published

A wrapper around the `@nrwl/jest` library that adds on the ability to run your tests from built artifacts rather than from libs (and deps) source.

Downloads

1

Readme

nx-jest

A wrapper around the @nrwl/jest library that adds on the ability to run your tests from built artifacts rather than from libs (and deps) source.

Installation

Npm npm i --save-dev @trellisorg/nx-jest

Yarn yarn add -D @trellisorg/nx-jest

Setup

Replace the executor in your projects configuration

Before:

{
    "targets": {
        "test": {
            "executor": "@nrwl/jest:jest",
            "outputs": ["coverage/packages/<package name>"],
            "options": {
                "jestConfig": "packages/<package name>/jest.config.js",
                "passWithNoTests": true
            }
        }
    }
}

After:

{
    "targets": {
        "test": {
            "executor": "@trellisorg/nx-jest:jest",
            "outputs": ["coverage/packages/<package name>"],
            "options": {
                "jestConfig": "packages/<package name>/jest.config.js",
                "passWithNoTests": true,
                "testFromSource": false
            }
        }
    }
}

Notice the testFromSource flag configured in the after example. This is what tells the executor to point all imports for a libraries dependencies to the pre-compiled artifacts in the dist folder.

This requires that all the library's dependencies be buildable and for all dependencies be built prior to tests being run. There are two ways to accomplish this:

  1. Set up the targetDependencies in your nx.json
{
    "targetDependencies": {
        "test": [
            {
                "target": "build",
                "projects": "dependencies"
            }
        ],
        "build": [
            {
                "target": "build",
                "projects": "dependencies"
            }
        ]
    }
}

Or if you are incrementally making your codebase buildable and cannot enable the target dependencies globally

  1. Add the dependsOn configuration to your libraries targets. Note: this will also need to be done all the way through the dep tree for your library so that all of your libraries dependencies are also configured so that when any libs build target through the chain is called all build targets for all libs are called.
{
    "targets": {
        "build": {
            "executor": "@nrwl/<type>",
            "outputs": ["{options.outputPath}"],
            "options": {
                "outputPath": "dist/libs/<package name>",
                "main": "libs/<package name>/src/index.ts",
                "tsConfig": "libs/<package name>/tsconfig.lib.json",
                "assets": ["libs/<package name>/*.md"]
            },
            "dependsOn": [
                {
                    "target": "build",
                    "projects": "dependencies"
                }
            ]
        },
        "test": {
            "executor": "@trellisorg/nx-jest:jest",
            "outputs": ["coverage/packages/<package name>"],
            "options": {
                "jestConfig": "packages/<package name>/jest.config.js",
                "passWithNoTests": true,
                "testFromSource": false
            },
            "dependsOn": [
                {
                    "target": "build",
                    "projects": "self"
                }
            ]
        }
    }
}

What this will do is tell Nx that when test is run for a lib to build that lib, and then Nx knows that when that lib has the build target called on it to also call build on all that libs dependencies, as long as this configured all the way through the tree then the build target will be called for all dependencies which would all be used by the test target instead of testing from source.