developing ts libs in deno world

When developing an npm module, it’s a well known standard to install the module locally (from another workspace) by npm link or simply npm install straight from a local directory. How does that look in Deno world? For example when developing a JSR module locally? Not much of a difference, actually. Here is my current […]

Read More developing ts libs in deno world

pass host’s stdin into docker container process and receive result at host’s stdout

Say we have a docker image, that we can run with e.g. And this command: And for obvious reasons, we don’t want to deal with volume mounting (it’s doable but if the command supports sdt streams, why bother with filesystem?) Then we actually have 2 different methods, one is a bit cleaner than the other. […]

Read More pass host’s stdin into docker container process and receive result at host’s stdout

postcss-design-tokens gotchas’

I remember when I worked constantly heavily with frontend cascading stylesheet topics, which was in the 2010s when people were simply converting Photoshop designs into HTML + CSS combos. Fast forward to today, lots of bells & whistles were definitely moulded on top of that flow. Style Dictionary is undoubtedly one of them, and even though I faced a bumpy start, I also got to relive those years of heavy frontend-oriented craftsmanship.

Read More postcss-design-tokens gotchas’

npmrc

Sometimes, when I run yarn for a project that uses a private dependency (whose registry access requires an auth token), I run into the 401 error: Usually this doesn’t happen if we have a proper .npmrc file somewhere up the root of the workdir (typically in the user home directory). But sometimes I am forced […]

Read More npmrc