js^Σ=8

Tooling choices are a subjective matter. Lately, I've been observing colorette taking over erroding chalk, and I have few thoughts on this subject.

Imagine the HTML: <a></b>.

Parser-wise, how would you design the AST architecture, considering cases like that?

One line in Babel config, env preset's loose set to true was causing a spread operator to disappear on only CommonJS builds (not ES Modules or UMD), which led to broken logic (program could not calculate opts.breakToTheLeftOf correctly any more), program inserted extra blank lines. A crazy bug, isn't it?

Back in the day, before native ES Modules, UMD builds were superior to IIFE because we could unit test them.

And while Rollup and Webpack can produce UMD, esbuild can only make IIFE, so that was an argument against using the esbuild.

A decade ago, Chris Coyier from CSS-Tricks described ways to consume SVG, which can be distilled into two groups: to link and to embed.

Fast forward to 2022, the market has shifted from WordPress+PHP to React+TypeScript, but the same dilemma "to link or to embed?" still applies because, at the bottom of it, we're still dealing with the same HTML and CSS as we did a decade ago.

So what's the best way to import SVG in MDX?

object-path is a getter/setter for nested arrays and plain objects. Here we use it directly and also align our API's to it. Here's why.

Consider a function written in TS, which multiplies two numbers...

Syntax highlighting is done using either highlight.js or prism.js. Once you've picked one, you'll have to set it up for code blocks: 1. within MDX and 2. outside MDX. That's how it works on all kinds of frameworks, not just Remix, although I'll post examples for Remix.

This setup is mostly a trivial task; however, there are a few niggles worth mentioning.