Alejandro Celaya | Blog

A couple of years ago I wrote about how to capture code coverage in API tests. In that article I explained the implications of code coverage collection when the code under test does not run in the same process as the test itself. However, the process explained there was a bit hacky and limited to AP…

After more than 10 months since v3.10.0 was released, with only a couple patch releases in between, and a lot of effort put into pushing this release out, in January 2024, shlink-web-client 4.0.0 has been finally released. As opposed to v3.0.0, which introduced many visual changes, v4.0.0 focuses on…

Recently, I migrated this very blog to Astro, and I took the opportunity to modernize the search system. I was then using lunr, which was a bit unmaintained, and not playing well with modern build tools. Introducing fuse.js Looking for alternatives I found fuse.js, a fuzzy-search library, with zero …

Context Around four years ago, I started to use Next.js in some projects, including this blog. These projects were not applications, but simple landing pages and documentation sites, where content written in markdown was a first class citizen. I remember that I was looking for a modern static site g…

I have always struggled with how packages are versioned and published to the npm registry. My main concern is that you probably want to also add a git tag to your source code when you are releasing a new version, but npm packages have their own versioning system, and include a "version" field in the…