JavaScript

I love DataDog, and I love CloudFlare, and If you're aggressively caching as we do, a good portion of requests won't ever make it to the origin, which is a good thing. However, a downside is that you'll likely miss out on having complete traffic logs. Fortunately, using CloudFlare Workers can help us solve this issue.

In React, passing data from a parent to its child is pretty simple, it can easily trickle down through props. But what about the other way around... without using Flux or PubSub?

So, let's say you have a few hundred ${guid}.zip or other files that uniformly match up to a data source but you need to rename them to something a little more friendly...

Uncover any unnecessary tags generated by the editor. This plugin adds the ability to toggle a trace on common parent block-level elements with an outline and their element name. The purpose for creating this plugin was so that it becomes a little clearer on what my WYSIWYG is doing.

During my adventures in learning React, I came across a particular roadblock with independent component communication. I understand how 'parent-child components' talk. The React doc's explain that pretty well. However, a place that could use an improvement is explaining with examples on how to make independent components communicate.

A simple approach to start automating with gulp!

Gulp is a robust javascript automation tool that uses a code-over-configuration, streaming build system that's powered by Node.