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-simple-reporter

v0.1.0

Published

Predictable simple format Jest reporter

Downloads

19

Readme

jest-simple-reporter

Cobbled together while I was trying to write an errorformat to use with Jest and Neomake in populating a Neovim quickfix window. This reporter just strips output down to a colon-separated list of values for each fixture.

Bound not to properly handle all situations. Really just a stop-gap until (hopefully) Jest implements a simplified output mode. Feel free to use and extend, PRs always welcome!

Install

npm -i --save-dev jest-simple-reporter

or

yarn add --dev jest-simple-reporter

Configure

Presuming you have Jest configured via package.json:

  "jest": {
    "reporters": [
      "jest-simple-reporter"
    ]
  }

Sample Output

/home/basie/foo/mobile/src/components/FlargleArgle/FlargleArgle.test.js:::I:FlargleArgle > Worfle:matches the last snapshot
/home/basie/foo/mobile/src/components/FlargleArgle/FlargleArgle.test.js:52:1:E:Expected value to be (using ===): 1 Received: <Loading />
/home/basie/foo/mobile/src/components/FlargleArgle/FlargleArgle.test.js:::I:FlargleArgle:returns a message when no flargles are available
/home/basie/foo/mobile/src/components/FlargleArgle/FlargleArgle.test.js:::I:FlargleArgle:marks the flargle read on touch
/home/basie/foo/mobile/src/components/FlargleArgle/FlargleArgle.test.js:74:3:E:Expected mock function not to be called but it was called with: Array [] 
/home/basie/foo/mobile/src/components/FlargleArgle/FlargleArgle.test.js:::I:FlargleArgle:calls fetchMore when scrolled to end of list

Currently I believe no line:col is available on test status 'passed', which could be rectified eventually.

Configuring Neomake

An errorformat that would work with this output might look like this:

let g:neomake_javascript_jest_maker = {
    \ 'exe': './node_modules/jest-cli/bin/jest.js',
    \ 'errorformat':
        \ '%f:%l:%c:%t:%m,' .
        \ '%-G%.%#'
    \ }
let g:neomake_javascript_enabled_makers = ['jest']

This just means:

  filepath:line:column:type:message
  ignore any non-matching line

Note that setting neomake_javascript_enabled_makers will override the default makers like eslint, so you might need to explicitly include those. It would also only display errors, since 'info' (I) lines generated by passing tests would be ignored by the second part of the errorformat. If I can find a way for the reporter to receive a line and column number, I'll update.

You could presumably use the errorformat string in a compiler for Vim too.