July 2020

While working on pico-tester I realized I am not as knowledgable in nodejs' support for ECMAScript Modules (esm).
I think it's very simple in the browser. There is <script type=module> which understands import and there is <script nomodule> which nicely gradually falls back to before ESM times. But what about nodejs? There is a package.json with properties such as main: <filename>, exports: {} type: module, type: commonjs, and any combination of them. For a long time I am using the package esm to allow me to use ESM on nodejs, but when publishing a package such as pico-tester, I must be compatible with as many ways as possible, in which nodejs can be used. So first there is terminology to get right (esm, cjs, ...) and than provide the right type of package or packaging so it can be used there. I might update this over time with more learnings.

I have this book Get Your Hands Dirty on Clean Architecture on my reading list, actually just as an open tab in my browser for a long time now. I just put it down here, maybe I come back to read it. Not sure if it is good and worth the time, but I like the topic and I think it is very relevant to understand this better.

It was the @standardsbot that made me learn and look up ValidityState. While that bot tweets weird stuff, there is always a learning in it. This time it was about ValidityState.