JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 4027
  • Score
    100M100P100Q109805F
  • License MIT

Elm-like architecture for React apps

Package Exports

  • react-palm
  • react-palm/tasks

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (react-palm) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

react-palm

Build Status

** This is very work in progress, please don't bother me about it, thanks. **

A cohesive strategy for managing state, handling side effects, and testing React Apps.

Strategy? Framework? Library?

It's very unlikely that you'll create a cohesive architecture if you piecemeal add requirements to an existing design.

react-palm takes a "subtractive" approach; we start with a full set of concerns and make sure that they work well together before breaking them up. This means that as your app grows, you won't have to rethink everything.

Should I use this?

Ideally, you should use Elm. This architecture is the closest thing to Elm I've managed to make within the constraints of JavaScript and React.

Choo looks good too.

license

MIT