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

react-most-spec

v1.1.0

Published

a spec util for react-most

Downloads

18

Readme

  • React Most Spec

Test utils for [[https://github.com/reactive-react/react-most][react-most]]

** install #+BEGIN_SRC sh npm install --save-dev react-most-spec #or yarn add --dev react-most-spec #+END_SRC

** Usage

*** sync mode async behavior is hardly predictable and not easy to reason, so if we can change it to sync behavior, it would be easier to write test.

To achieve that, we can simply replace most engine with a fake sync one. #+BEGIN_SRC js import {stateStreamOf, stateHistoryOf, intentStreamOf, intentHistoryOf, run, dispatch, Engine } from 'react-most-spec'; let counterWrapper = TestUtils.renderIntoDocument( ) let counter = TestUtils.findRenderedComponentWithType(counterWrapper, Counter) counter.actions.inc() counter.actions.inc() counter.actions.inc() expect(stateHistoryOf(counter)[2].count).toBe(3) #+END_SRC

*** async mode if you want to test with real engine, simply not parse the fake =Engine= from =react-most-spec= #+BEGIN_SRC js spyOn(console, 'error') let counterWrapper = TestUtils.renderIntoDocument( ) let counter = TestUtils.findRenderedComponentWithType(counterWrapper, Counter) return run(intentStreamOf(counter), dispatch([{type: 'exception'}], counter), [ state=>expect(console.error).toBeCalledWith('There is Error in your reducer:', 'exception in reducer', undefined) ]) #+END_SRC

=run= will return a promise, so simply return it and jasmine will wait for the promise resolved.

the 3 parameters are source stream:Stream, async actions:Promise, expects: Array[Function]

=Function= in =expects= should be in the same order of the value in source stream