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

@ticketmaster/allure-mock

v4.0.28

Published

Allure common mocking solution library

Downloads

1,130

Readme

@ticketmaster/allure-mock

Allure common mocking solution library.


This library is a collection of shared mocking middlewares to mock shared services inside an Allure project.

To use them, you need to have Mirage JS installed on your project. If it's not the case, we gonna install it with allure-mock.

Usage

1. Install dependencies

First, you need to install the dependencies.

# Optional. Only if you don't have miragejs on your project
yarn add miragejs -D

yarn add @ticketmaster/allure-mock -D

2. Create the mock server creator

If you don't already have one, you have to create a function to instantiate a mock server. This function will be called later if we need to mock calls.

We recommend to put this file at the root of your src folder and call it mock.ts.

// src/mock.ts

import { createServer } from "miragejs";
import type { Server } from "miragejs";
// Import a mocking middleware
// In this case this is the identityMock middleware that mock the identity service
import { identityMock } from "@ticketmaster/allure-mock";
import { featureFlagMock } from "@ticketmaster/allure-mock";

export const createMockServer = ({ environment = "test" } = {}): Server => {
  const server = createServer({
    environment,
  });

  // This is how we apply a mocking middleware
  // All your calls will go from top to bottom. So the order application of the middlewares is important
  // A mock middleware only take one parameter, the server instance
  identityMock(server);
  featureFlagMock(server);

  // Allow unhandled requests to pass through
  // see: https://miragejs.com/api/classes/server/#passthrough
  server.passthrough();

  return server;
};

3. Instanciate the mock server

Then, inside your application root file (which is probably here: src/pages/_app.tsx), you gonna have to instantiate your mock server in certain circumstance. For example, when the environment variable MOCK exist and is true.

// src/pages/_app.tsx

import React from "react";
import type { AppProps } from "next/app";
import { AppProvider, AppProviderProps } from "@ticketmaster/allure-core";
import { createMockServer } from "@src/mock";

if (process.env.MOCK === "true") {
  createMockServer({ environment: process.env.NODE_ENV });
}

...

If you need more granularity, for example you want certain mock middlewares to be activated only in certain circumstance, you should put this logic inside your createMockServer function.