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

dynamic-hoc-connect

v0.1.0

Published

A wrapper for react-redux connect HOC that allows mutation of its arguments.

Downloads

1

Readme

dynamic-hoc-connect

A wrapper for react-redux#connect HOC that allows mutation of its arguments.

This module provides the ability to change the arguments to connect at runtime, triggering the connected component to re-render.

The primary purpose of this function is to provide the ability to write unit tests for React components in isolation from the Redux store. While the developer can export both the original component and the connected component, this technique does not apply if any of the component's descendants are connected to the store. With dynamicConnect, each wrapped component can have its arguments (such as mapStateToProps and mapDispatchToProps) replaced with mock functions in the test suite.

Example

Components

import React from 'react'
import { dynamicConnect } from 'dynamic-hoc-connect'

const TodoList = ({ todos }) => (
  <ul>
    {todos.map(todo => (
      <li key={todo.id}>
        <TodoContainer todo={todo} />
      </li>
    ))}
  </ul>
)

export const TodoListContainer = dynamicConnect(
  state => ({ todos: state.todos }),
  () => ({}),
)(TodoList)

const Todo = ({ creator, onComplete, todo }) => (
  <div>
    <span>{todo.text}</span>
    <span>Created by {creator.name}</span>
    <button onClick={onComplete}>Complete</button>
  </div>
)

export const TodoContainer = dynamicConnect(
  (state, props) => ({
    creator: state.users.find(user => user.id === props.todo.creatorId),
  }),
  (dispatch, props) => ({
    onComplete: () =>
      dispatch({
        type: 'COMPLETE_TODO',
        todo: props.todo,
      }),
  }),
)(Todo)

Tests

import { createStore } from 'redux'
import { Provider } from 'react-redux'
import React from 'react'
import { render } from '@testing-library/react'
import { spy } from 'sinon'
import test from 'ava'

test('TodoListContainer', t => {
  const store = createStore(state => state, {})

  const testTodos = [
    { creator: '1', id: '42', text: 'foo' },
    { creator: '2', id: '43', text: 'bar' },
  ]

  const testCreators = {
    '1': { id: '1', name: 'Mary' },
    '2': { id: '2', name: 'Steve' },
  }

  const onComplete = spy()

  // Replace `mapStateToProps` with a method that returns
  // the expected props. To test the logic of the actual
  // `mapStateToProps` function, export and test it
  // separately or use selectors from the `reselect`
  // library.
  TodoListContainer.args.mapStateToProps = () => ({
    todos: testTodos,
  })

  TodoContainer.args.mapStateToProps = (_, props) => ({
    creator: testCreators[props.todo.creator],
  })

  TodoContainer.args.mapDispatchToProps = () => ({
    onComplete,
  })

  // Because it wraps the original `connect` function,
  // we must render a `Provider` or `react-redux` will
  // throw an error.
  const { getByText } = render(
    <Provider store={store}>
      <TodoListContainer />
    </Provider>,
  )

  getByText('foo')
  getByText('Created by Mary')
  getByText('bar')
  getByText('Created by Steve')

  TodoListContainer.args.mapStateToProps = () => ({
    todos: [testTodos[0]],
  })

  t.throws(() => {
    getByText('foo')
  })

  TodoListContainer.restoreArgs()
  TodoList.restoreArgs()
})

API

dynamicConnect(mapStateToProps[, mapDispatchToProps[, mergeProps[, options]]])

Arguments

See react-redux#connect docs.

Return value

Component => WrappedComponent

The WrappedComponent has additional properties for mutating the connect arguments at runtime, which will re-render any component instances:

  • args.mapStateToProps
  • args.mapDispatchToProps
  • args.mergeProps
  • args.options

The arguments can be restored to their originally provided values with the restoreArgs method.