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-serializer-functions

v1.0.6

Published

Jest serializer for functions

Downloads

11

Readme

jest-serializer-functions

Jest snapshot serializer for functions. Read more about snapshotSerializers

Background

Whenever you are using Jest for snapshot you may notice that functions will appear in snapshots in different ways. If the function is mocked you will see it as:

  • [Function]
    • when the function is not mocked with Jest
    • when you have React component that has a function inside JSX (consumers)
  • [MockFunction]
    • when the function is mocked with jest, usually implementation is: myFn = jest.fn()
  • [MockFunction <<function-name>>]
    • where <<function-name>> is the name of the function
  • [MockFunction] {calls: [] results: []}
    • when the mocked function was called previously

How it works

This serializer will help you have a more consistent way of viewing functions as every time will return [Function] as the base.

If the function has a name it will serialize it as [Function] <<function-name>>. As the part where the function is mocked or not just adds noise to the important part.

Now the good part :astonished: is when you are using this serialiser with (React)[https://www.npmjs.com/package/react] (and enzyme) as it will improve what you can see in the snapshot. Take as example source code:

<Context.Consumer>
  {
    (handler) => (
      <Subscriber
        handler={handler
      />
    )
  }
</Context.Consumer>

this will result in a snapshot that will look like:

<Context.Consumer>
  [Function]
</Context.Consumer>

I would not say this is very helpful (if I change something from the function nothing will break in my snapshot). This serializer will return:

<Context.Consumer>
  () => (<Subscriber
    handler={handler}
  />)
</Context.Consumer>

Installation

npm install --save-dev jest-serializer-functions

Or if you are using yarn

yarn add --dev jest-serializer-functions

Usage

Having jest config as json

// jest.json
{
  ...
  "snapshotSerializers": [
    "jest-serializer-functions"
  ],
  ...
}

Having jest config as json inside package.json

// package.json
{
  ...
  "jest": {
    ...
    "snapshotSerializers": [
      "jest-serializer-functions"
    ],
    ...
  },
  ...
}

Take into consideration

Everything has pros & cons.

Pros

This serializer will help you with a better understanding of your functions and fail tests that until now passed when doing partial refactoring.

Cons

The time to execute your tests will increase (depending on how many snapshots you have like this).

The space used by snapshot will increase, as more data will be stored.

Contributing

Pull requests and issues are welcome :heart:.