jackdbd/calderone

My personal TypeScript monorepo

Hi there, I'm Giacomo 👋

I am a freelance full-stack developer from Italy 🇮🇹.

Welcome to my GitHub profile!

💻 Gists 'N Repos

calderone - TypeScript monorepo I use to develop most of my npm packages and try out new stuff.
undici - monorepo for my 11ty plugins.
matsuri - monorepo for my hapi.js plugins.
personal-website - personal website and blog, built with 11ty and Workbox. Hosted on Cloudflare Pages.
nix-config - NixOS and Home Manager configurations for my machines.
zig-cairo - Thin, zig-idiomatic wrapper for the Cairo graphics library.
path-tracer - Implementation of Peter Shirley's Ray Tracing in One Weekend in the Zig programming language.
skija-samples - Repo I use to learn how to use Skija in Clojure.
talks - Talks and presentation I gave at conferences and meetups.
dotfiles - My personal Linux dotfiles, symlinked to my home directory with GNU Stow.
Minimal XCB + Cairo example in Zig (gist)
Function reflection in Zig (gist)

🔍 Find me on the internetz

🌎 Personal site & blog
🐦 Twitter
💼 LinkedIn
📚 Stack Overflow

📝 Selected blog posts

• Auditing an eCommerce website
• Performance audit of an Italian news website
• Test your JavaScript on multiple engines with eshost-cli and jsvu
• Generate and view HAR files
• 3 ways to solve the expression problem
• Inspect container images with dive
• A few timeless lessons from Peopleware

📚 Books I'm reading

• The Razor's Edge
• Purely Functional Data Structures
• Mazes for Programmers: Code Your Own Twisty Little Passages
• Practical Binary Analysis: Build Your Own Linux Tools for Binary Instrumentation, Analysis, and Disassembly
• Articulating Design Decisions: Communicate with Stakeholders, Keep Your Sanity, and Deliver the Best User Experience

More books on my goodreads profile.

calderone's Issues

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://europe-west3-npm.pkg.dev/prj-kitchen-sink/npm-registry/.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀