I've spent the majority of this week learning the React/Redux workflow as it's what we use on our webapp at Pluot. Generally speaking, the idea behind the architecture is pretty solid and can summed up thusly: keep all your state in one place, you filthy animal, and pub/sub/observe/notify any updates.
There. You now understand Redaxt.
I really have nothing much to say about npm as if you've ever used it you'll understand intuitively my point, but for those of you who have never used it, I will briefly explain the horror.
Given the correct flag, webpack will re"compile" your files when they're changed but I have yet to figure out what heuristic it's using to trigger a rebuild, given how randomly it actually works as intended. Your mileage may vary, but if you figure this out please someone let me know how it's supposed to work. To add insult to injury, the build output doesn't include anything so useful as a timestamp so that you can easily tell when the last time it deigned to run was.
Functional Programming Cargo Culted Fanfic, aka The Redux Docs
Here are a few curated selections:
"It's very important that the reducer stays pure." like a virgin, until you touch it for the very first time. Or actually no, don't ever touch it because then it will not be pure and how could you do that to a function?
"No surprises. No side effects. No API calls. No mutations. Just a calculation." asking for a boy to love him.
"let's start writing our reducer by gradually teaching it to understand the actions we defined earlier", oh noble Pygmalion.
"Redux will call our reducer ... for the first time. This is our chance...", your once in a lifetime opportunity!
"Here is our code so far. It is rather verbose:" This statement was followed by the least verbose code I've seen. I do not understand what the word 'verbose' means to anyone in this universe.
"we can split the reducers into separate files and keep them completely independent" as separate files are a recognized talismic barrier for keeping code from becoming logically entangled.
Or maybe I'll just try Elm. I hear its compiler is very nice.
 Great if you like syntactic sugar bullshit that is the opposite of readable.