ambidex

The first time I used Promises (and really, the first time I did any serious work in Node), I prototyped an isomorphic web server: https://github.com/appsforartists/ambidex/blob/master/src/Am... In three different places in that file, you'll find a Promise that ends in ".catch(error => console.error(error.stack))`. Before I learned that bit of boilerplate, I'd spend an hour staring at my screen wondering why things were silently broken. It's mindblowing that errors are implicitly suppressed by default with Promises. console.error ought to be automatically invoked for any error that makes it to the root scope without a .catch() (just like it is with sync code).

It's a service-oriented architecture. The API is not your web server. You can use something like Ambidex to render HTML from your React components on the web server, backed by your WP-API. ------ More info (in video form): https://www.youtube.com/watch?v=yaymfLj5tjA Ambidex (one of many ways you could implement this paradigm): https://github.com/appsforartists/ambidex

Work-related: - Spoke at a conference for the first time (React.js Conf) [1] - Released my first serious open-source project (an isomorphic React app server) [2] - The project I've been building was demoed to some executives and put our team in a really good spot. Other cool stuff: - Started buying furniture and accessories to make my room feel like home. I've always been hesitant to own large items because I've moved pretty frequently since I finished high school. Buying a handmade hardwood bed is a big deal for me. [1]: http://conf.reactjs.com/schedule.html#tweak-your-page-in-rea... [2]: https://github.com/appsforartists/ambidex/

I'm also experimenting with isomorphic React apps. I'll be presenting some of my work at React Conf at the end of the month (so this isn't yet as well documented as it should be), but here's what I'm trying to handle async data with ReactRouter: - Have the data your view depends on expressed as a named parameter in routes.jsx: https://github.com/appsforartists/ambidex-example--bike-inde... - Use those named parameters to resolve which stores need to be populated before rendering: https://github.com/appsforartists/ambidex-example--bike-inde... - Don't render the page on the server until those routes are populated: https://github.com/appsforartists/Ambidex/blob/master/src/ca... In that example, the editBike view depends on bikeID. actionsForRouterState makes sure that the viewBike action is called to populate the CurrentBike store before