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

msw-snapshot

v5.2.0

Published

Transparently create an API cache for testing.

Downloads

58

Readme

msw-snapshot

Transparently create an API cache for testing.

Install

$ npm i -D msw msw-snapshot

Configuration

import { setupServer } from 'msw/node';
import { snapshot } from 'snapshot'

type Info = {
  request: Request;
  cookies: Record<string, string | string[]>;
  context: { namespace: string };
}

const server = setupServer(
  snapshot({
    /**
     * Specify the directory path to store snapshot files.
     */
    basePath: string;

    /**
     * Specify msw's handler RegExp.
     */
    test?: RegExp; // default: /.*/

    /**
     * Specify whether to update snapshot or not.
     */
    updateSnapshots?: boolean | 'none' | 'all' | 'missing'; // default: false

    /**
     * Specify whether to ignore existing snapshot or not.
     */
    ignoreSnapshots?: boolean; // default: false

    /**
     * Callback when response is received from server.
     */
    onFetchFromServer?: (info: Info, snapshot: Snapshot) => void;

    /**
     * Callback when response is received from snapshot.
     */
    onFetchFromSnapshot?: (info: Info, snapshot: Snapshot) => void;

    /**
     * Callback when snapshot is updated.
     */
    onSnapshotUpdated?: (info: Info, snapshot: Snapshot) => void;

    /**
     * Create request identifier.
     */
    createSnapshotPath?: (info: Info) => Promise<string>;
  })
);

server.listen();
// The all requests are snapshotted.
server.close();

Recipe

FAQ

How should I use createSnapshotPath?

You can control the snapshot directory layout via this.

For example, if you want to create snapshot files that should be located per request host and pathname, you can use the following configuration.

snapshot({

  ...

  createSnapshotPath: async (info) => {
    const url = new URL(info.request.url);
    return [
      url.host,
      url.pathname,
      toHashString([
        info.request.method,
        url.origin,
        url.pathname,
        getSortedEntries(maskURLSearchParams(url.searchParams, ['t'])), // this
        getSortedEntries(info.request.headers),
        getSortedEntries(info.cookies),
        new TextDecoder('utf-8').decode(await info.request.arrayBuffer()),
      ])
    ].join('/');
  },

  ...

})

For another use-case, if you want to create snapshot files for each vitest/jest test-cases, you probably use the following configuration.

import { context, snapshot } from 'msw-snapshot';
import { beforeEach } from 'vitest';

beforeEach(ctx => {
  context.namespace = ctx.expect.getState().currentTestName;
})

const fetchCountMap = {};

snapshot({

  ...

  createSnapshotPath: async (info) => {
    fetchCountMap[info.context.namespace] = fetchCountMap[info.context.namespace] ?? 0;
    fetchCountMap[info.context.namespace]++;
    return `${info.context.namespace}-${String(fetchCountMap[info.context.namespace]).padStart(3, '0')}`
  },

  ...

})

How should I use mask*** functions?

For example, if your app appends cache busting query like t=${Date.now()}, msw-snapshot will take unexpected snapshots.

In this case, You can control snapshot identity via createSnapshotPath.

import { snapshot, toHashString, maskURLSearchParams } from 'msw-snapshot';

snapshot({

  ...

  createSnapshotPath: async (info) => {
    const url = new URL(info.request.url);
    return [
      url.host,
      url.pathname,
      toHashString([
        info.request.method,
        url.origin,
        url.pathname,
        getSortedEntries(maskURLSearchParams(url.searchParams, ['t'])), // this
        getSortedEntries(info.request.headers),
        getSortedEntries(info.cookies),
        new TextDecoder('utf-8').decode(await info.request.arrayBuffer()),
      ])
    ].join('/');
  },

  ...

})