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

@uwhealth/netlify-plugin-jest

v1.0.0

Published

Netlify Build plugin - Netlify plugin to run Jest unit tests and set status in GitHub.

Downloads

4

Readme

Netlify Plugin - Jest

Netlify build plugin to run Jest unit tests and set a simple status in GitHub on the commit that triggered the build. Failed tests will stop the build so no build time is wasted.

Jest unit tests are run via a simple command line before the build (onPrebuild). The json results are extracted to get some summary info. GitHub status messages are set when tests start and with the summary when finished. If the tests fail, the plugin cancels the build. If there are plugin or other errors the build will be failed. Otherwise, the build will proceed.

The Github status details link will go to the Netlify deploy log, so someone can see details on the failed tests or errors.

Install (manual)

npm install netlify-plugin-jest

Usage

Add this plugin to the plugins array in your netlify.toml configuration file:

[[plugins]]
package = "netlify-plugin-jest"

  [plugins.inputs]
  # all inputs for this plugin are required, but have default values

Configuration

The plugin requires a GitHub personal access token to be set as an environment variable named GITHUB_PERSONAL_TOKEN . It is used to set a simple GitHub repo status.

  • name: testCommand
    • description: The command line used to trigger the tests and any other features. Separating this out allows for easier customization and future development. Change cautiously.
    • default: jest --collectCoverage --json --outputFile jest.results.json
    • required: true
  • name: skipTests
    • description: Skip unit tests but leave the plugin present
    • default: false
    • required: true
  • name: skipStatusUpdate
    • description: Skip Github status updates
    • default: false
    • required: true
  • name: testFailureErrorMessage
    • description: String that exists inside of the error message indicating tests failed.
    • default: Command failed with exit code 1
    • required: true
  • name: gitHubStatusName
    • description: Context/name for the status in GitHub, should be pretty unique
    • default: Jest Tests
    • required: true
  • name: extraLogging
    • description: Display some extra console logging.
    • default: false
    • required: true

Development

Explanation of the plugin's logic

  1. Checks if configured to skip tests

  2. Sets a GitHub status of pending/running...

  3. Run the testing command

  4. Determine success, plugin error or testing failure. Testing failure is soley deteremined by the presence of the testFailureErrorMessage string in the error response. This is because all regular testing failures are still returned as errors.

  5. If success: a. Set the GitHub status b. Continue on building

  6. If testing failure: a. Parse the test results that are written to a json file and construct a short summary for the GitHub status. b. Set the GitHub status c. Cancel the Netlify build

  7. If other error: a. Set the GitHub status b. Fail the Netlify build

Develop Locally

The plugin can be developed locally most easily by including it as a relative path in another locally functioning Netlify site that is linked to Netlify.

Example netlify.toml for local site to reference the local plugin (plugin-local-install-core is necessary)

[[plugins]]
package = "..\\netlify-plugins\\netlify-plugin-jest\\"

  [plugins.inputs]
  extraLogging = true

[[plugins]]
package = "@netlify/plugin-local-install-core"

Remember the GITHUB_PERSONAL_TOKEN needs to be set in the local Netlify site not the plugin itself. This will allow netlify build on the Netlify site (not the plugin) to run the plugin. It will also set the status on the commit for the the site's repo if there is a pull request present. Not all Netlify environment values are present locally: DEPLOY_URL etc.

Testing plugin on an actual Netlify Build/Deploy without a released npm

The plugin can be tested without using an actual released npm package by doing the following:

  1. Figure out the branch/tag/commit etc of the plugin to test, and install it as a package in the Netlify site you will use for testing: npm install UWHealth/netlify-plugin-jest#<branch/tag/commit>

  2. Change the Netlify site's toml configuration:

    [[plugins]]
    package = "./node_modules/netlify-plugin-jest"
    
      [plugins.inputs]
      extraLogging = true
    
    [[plugins]]
    package = "@netlify/plugin-local-install-core"
  3. Make sure to clear the build/deploy cache when you build/redeploy the testing site on Netlify. This will pull down a clean copy of the plugin code from the branch/tag/commit specified in the package.json after the npm install.

  4. Uninstall the Github sourced npm afterwards if the site is to be used for production purposes.

Future Ideas

  • Configure the plugin to use a Github App.

  • Set test failure information as annotations on files in the form of more advanced GitHub Status Check.

  • Display Jest testing coverage information on GitHub repo.