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

@twy-gmbh/angular-vanity-builder-jest

v1.0.5

Published

You have an existing project and integrated `Jest` all by yourself? **Awesome**.

Downloads

2

Readme

ng test -> running jest

You have an existing project and integrated Jest all by yourself?
Awesome.

Your ng test command is broken and you can not use any builder (be it @nrwl/jest or @angular-builders/jest) without messing up your already existing setup. All you want is for ng test to execute jest with your existing configuration.

npm version npm

This documentation is for version 8 only.

Allows running ng test with your currently working Jest configuration.

Prerequisites

Folder structure

This builder expects the following structure:

...
projects/
    project1/
        jest.config.js
    project2/
        jest.config.js
...

Installation

Install the builder (and jest if you still haven't): npm i -D jest @types/jest @twy-gmbh/angular-vanity-builder-jest

Running with Angular CLI

  • In your angular.json:

    "projects": {
        ...
        "[your-project]": {
          ...
          "architect": {
              ...
              "test": {
                  "builder": "@twy-gmbh/angular-vanity-builder-jest:run"
    
  • Run the tests: ng test or ng test [your-project]

Zero additional configuration is needed since all of your configuration is already where it actually belongs, the jest.config.js files.

With this structure, you can cd into a project folder, and use the Jest cli to run the tests via jest. You can now also use ng test in the root folder, this will run the tests for all projects.

ng test project1 on the other hand let's you execute the specific test suite of said project.