Ecosystem'd
The past few weeks I have been working on a few applications with Raj. I like where things are going.
raj-compose
Things were taking shape and raj/effect
was growing to be a chokepoint for the development of raj-spa
and the applications which used it directly. I broke raj/effect
into its own module raj-compose
to better tackle composition problems without conflicting with core development.
Migrating:
// BEFORE
import {map, batch} from 'raj/effect'
map(callback, effect)
batch(effects)
// AFTER
import {mapEffect, batchEffects} from `raj-compose`
mapEffect(effect, callback) // NOTE: arg order reversed
batchEffects(effects)
raj-react
React has been a first-class citizen since the beginning of Raj development. Raj has always been view library agnostic and breaking React support into a separate module makes that clearer.
Migrating:
// BEFORE
import {program} from 'raj/react'
// AFTER
import {program} from 'raj-react'
These packages and raj-spa
are now listed in the README "Ecosystem" section.