JavaScript

A little reminder from Matt Smith that getting the last item in an Array is easier now:

Josh Comeau does a great job with beginner-friendly explanations of important concepts, and Promises From The Ground Up is no exception. In a nutshell, we have Promises because we need callbacks. We need callbacks because JavaScript is single-threaded and can’t wait around for things. And so we dance. These days, you’ll see more async and […]

Feels notable that Iterator helpers have become Baseline Newly available. The gist is that you can map and filter on stuff that was annoying or impossible to before. I’ll copy Jeremy Wagner’s example:

I was trying to play with CSS Module Scripts the other day, which are a way to import CSS as a constructable stylesheet using the ESModules syntax. They are Chrome-only so not really something we can generally use (unless you’re building an Electron app or something), but I really like the idea of being able […]

Just a tiny gotcha.

We can pass the mouse position from JavaScript to CSS and use it to make unusual and playful effects.

A bit of a pivot from the Redwood gang, splitting RedwoodJS into Redwood GraphQL … To minimize disruption and provide clarity going forward, we’re renaming the existing RedwoodJS framework to Redwood GraphQL, reflecting its strength as a mature, stable framework built around GraphQL. … and the newfangled RedwoodSDK. Redwood has always been ultra opinionated (I […]

Matt Smith on when to use map() vs. forEach() in JavaScript. Just one of those things I can imagine asking or being asked in a coding interview. Some interesting comments below the article as well.

It’s not particularly obvious, but a child’s useEffect will run before a parent’s will. Let’s look at why.