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

redux-elmish

v0.4.0

Published

The Elm Architecture in Redux, statically checked using flow

Downloads

4

Readme

The Elm Architecture in Redux, statically checked using flow

Atempt to be as close as possible to Elm Architecutre in means of composition and static typing, and not lose Redux good parts (devtools) in the process.

Static typing

Following parts are statically type checked with flow:

  1. init and update functions input and result

  2. view props

  3. action creation, both on view events and effects results (tagged action creation is also checked, when composing views and effects). This is achieved with disjoint union static-typing

  4. action type exhaustiveness checking static-typing

Effect handling

Slight variation implemented on top of redux-loop, so it can be statically type-checked.

Devtools

Full hot reload and time travel compatibility. Keeping it that way is of high priority

TODO: Tagged actions pretty print

How to use?

Please check the famous Elm nesting examples