Axel Rauschmayer

@rowe-morehouse You have to click on the heading (“front side”) in order to expand the body (“back side”).

It would indeed be great to have this! Any progress? IMO, the most important things are: distinguishing single backticks and triple backticks (including their “type tag”) and tables.

My use case is static site generation: The same code has to run on the client and in Node.js. And currently `new URL(relPath, import.meta.url)` is the best cross-platform pattern for...

I’d start with minimal functionality and see where it goes. My feeling is that how URLs work should stay as close to uncompiled code as possible, which would indeed mean...

I ended up doing the following: ```css @media screen { .sourceCode { overflow: visible !important; white-space: pre-wrap !important; } } ``` Wrapping was necessary because Books.app would cut off text...

This would go together well with paging. For my own blog, I have one feed page per year. That helps with incrementally updating the feed.

I haven’t used it, yet. I was mainly intrigued by the possibility of a WebAssembly version (and how portable such a version would be), given that Packem is implemented in...

Note that name-importing from CommonJS works if the exports look like this ([more information](https://2ality.com/2022/10/commonjs-named-exports.html)): ```js exports.namedExport = 'yes'; ```

@OnlyDeLtA Why? Easy to check: run this code (with a semicolon) in a browser console or the Node.js REPL.

> I tried to figure out what existing declarations really mean, maybe it's about hoisting thing. But then I realized that this is actually named function expression and named class...