Redux sagas for Google YOLO

I've been working for a bit lately to get into React. Initially, I had built the stack: webpack, React, Redux, etc, all by hand. At some point I got over confident, and thought I was ready to go into the deep end. At that point, I swapped over into react boilerplate to 'really' develop something. Huge points won me over, hot reloading, 'some' guidance on the way it should be configured, and community to draw from.

Displaying date input values using javascript

A minor annoyance you might not consider at first working with HTML 5 date type inputs:

The date display is what the user is thinking. Say: Oct 31st, 2008 translating to their locale. For me, that's 10/31/2008.
The input's value will be: "2008-10-31" - Makes perfect sense.
The input's valueAsDate will be: "2008-10-29 18:00:00 -0600 CST" - Errr... What?


Redux and Vanilla JS

Redux is a rather famous part of the React ecosystem, but it doesn't have to be. All of the logic arguments for Redux stand on their own apart from the rendering engine you pair with it. In the past, I've emulated Redux-like data stores in Angular 1.x apps, and hand rolled solutions. They do one thing, and they do it really well, manage state. There's always arguments for spawning multiple Redux stores of the best I've heard was one store per API consumed as a cache.

Sample NPM package.json for Drupal

I've recently started to dump build tools. The abstractions just aren't needed, and add complexity in some cases. To that end, I'm nearly doing all my asset management in package.json with NPM scripts. For existing sites I'm maintaining, I can use this as a simple drop in to help get started. It may require a little modification site to site, depending on if you need to ignore certain themes, or modules. But, I think the base package here is clear enough you'll be able to replicate the pieces required.


Subscribe to RSS - javascript