JavaScript, Page 3

You may have heard that you should be “linting” your code. What does that mean? Why would you want to do it?

Join me in exploring a recent experience where I started with flawed logic (without realizing it) and the steps I took to fix my bug. Let’s experience some broken code together. 🎉

Development toolchains now have many more layers of tools than they did years ago. Because of this change, the JS code that runs in our users' browsers looks less like the original code we authored. Periodically checking the code generated by our tools can lead to opportunities to reduce bundle size and improve performance for users.

We do a lot of rapid prototyping at Cloud Four, which means we’re often working with incomplete or hypothetical content. When it comes to FPO images, we’ve relied on a few different solutions: Third-party services…

For a recent project, we built an isomorphic application with Nuxt.js. It was important for our app to function for users even if they were offline, so I got to work on turning…

As a JavaScript developer, I’m used to my code running differently in different environments. But earlier this week, I ran into a problem that left me scratching my head for most of the morning. I…

Apple has started development of service workers—the key technology powering Progressive Web Apps.

Here’s a neat little solution to a problem I encountered in my quest to use more animation in my interface design work. I was prototyping a sliding view transition between nested levels of…

A project opportunity combined with my own curiosity allowed me to get a better understanding of Handlebars partials. Turns out you can do much more than I was aware of.