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

@gpx/render-composer

v3.2.0

Published

Create complex renders for react-testing-library

Downloads

26

Readme

The problem

When working with Testing Library within a large project often you need to wrap your component in several providers:

const history = createMemoryHistory();
const locale = 'en';
const user = {name: 'Giorgio'};
render(
  <Router history={history}>
    <IntlProvider locale={locale}>
      <UserContext.Provider value={user}>
        <MyComponent />
      </UserContext.Provider>
    </IntlProvider>
  </Router>,
);

This can lead to a lot of overhead and is not very flexible.

The solution

Render Composer allows you to declare reusable and configurable wraps that define a single provider. These wraps can then be combined to generate more complex hierarchies.

const RouterWrap = wrap((children, {history}) => (
  <Router history={history}>{children}</Router>
)).defaultData(() => ({
  history: createMemoryHistory(),
}));

const IntlWrap = wrap((children, {locale}) => (
  <IntlProvider locale={locale}>{children}</IntlProvider>
)).defaultData({locale: 'en'});

const UserWrap = wrap((children, {user}) => (
  <UserContext.Provider value={user}>{children}</UserContext.Provider>
)).defaultData({user: {name: 'Giorgio'}});

const appRender = RouterWrap.wraps(IntlWrap)
  .wraps(UserWrap)
  .withRenderMethod(render);

appRender(<MyComponent />);

Installation

With NPM:

npm install @gpx/render-composer --save-dev

With Yarn:

yarn add @gpx/render-composer --dev

Now simply import it in your tests:

import wrap from '@gpx/render-composer';

// or

var wrap = require('@gpx/render-composer');

Usage

You can create a wrap with the wrap method:

const Wrap = wrap((children, data) => <div>{children}</div>);

data is an empty object by default. You can set some default values with defaultData:

Wrap.defaultData({foo: 'bar'});

If you need the data to be generated every time rather than be static you can also pass a function to defaultData:

Wrap.defaultData(() => ({foo: Math.random()}));

You can compose the wraps with the wraps method. You can chain as many wraps you want:

WrapA.wraps(WrapB)
  .wraps(WrapC)
  .wraps(WrapD);

Once you are satisfied with your wrap you can get a render method with withRenderMethod:

import {render} from '@testing-library/react';

const renderWrap = Wrap.withRenderMethod(render);

renderWrap(<MyComponent />);

The generated render method will also accept data to overwrite the default values you defined in your wraps. The data will be returned too:

Wrap.defaultData(() => ({foo: 'bar'}));

// This `foo` will have value `'bar'`
const {foo} = renderWrap(<MyComponent />);

// This `foo` will have value `'baz'`
const {foo} = renderWrap(<MyComponent />, {foo: 'baz'});

Note that wraps are immutable so that they can be defined in one file and exported and combined.