JavaScript

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.

What is the difference between ESLint and TypeScript? Perhaps that feels like a strange question as ESLint is a, uhm, linter, and TypeScript is a language that compiles to JavaScript. Josh Goldberg writes how there is some overlap: While ESLint and TypeScript operate differently and specialize in different areas of code defects, there is some […]

I enjoyed this blog post from Blake Watson about a simple requirement and then going down the rabbit hole of functional programming to solve it in increasingly reusable, if mind-bending ways. By the end: Creating a function that returns a function that returns a function can get a little trippy to think about. But what […]

Allen Pike “after about a decade away from regularly writing JavaScript” comes back to take a look. I think these points are all correct: The goal was to see if there was an obvious (boring, trodden) framework, and the answer is… kinda?