Node.js is where most of my TypeScript runs — in AWS Lambda functions, in containers, and in the build and test tooling around them. I’ve shipped production Node.js systems on contract and published several open source npm packages of my own.
How I approach Node.js projects
I write TypeScript rather than plain JavaScript, in strict mode, so type errors are errors. I keep dependency counts low — every package you add is a package someone has to keep patched — and I set up the deployment pipeline in the first week, because a project that’s awkward to deploy is a project that stops moving.
Because the same language runs the service, the tooling and the front end, you don’t need to hire separately for each of them or wait on a handover between people. That is usually what decides whether a date holds.
Open source npm packages
The four that come up most on Node.js work, all published under the @kensio
scope and open to read:
- @kensio/yulin — simulates AWS in-process for fast, isolated tests.
- @kensio/smartass — assertion functions that narrow types properly.
- @kensio/part-factory — test object factories without the boilerplate.
- @kensio/colophon — generates social meta images for static sites.
The rest, including the Claude Code skills, are on the open source page.
Publishing packages keeps me honest. The code is out in the open, and it has to hold up.
Node.js work I’ve delivered
- Freetrade — Principal Software Engineer on a serverless Node.js platform running on Google Cloud Functions.
- Fanalysis — Node.js services on AWS, as second employee and Staff Engineer.
- Bulb — contract engineer working in Node.js and TypeScript alongside Kubernetes and Terraform.
Hire a freelance Node.js developer
Contact me about your Node.js project, from a single service to a complete MVP.