05Open source

Useful tools, openly shared.

Small TypeScript libraries, with the source available to read, use, and build on.

01 / PUBLIC PACKAGES

Open-Source Work

TypeScript libraries for specific development tasks. Explore the packages, read the source, and use what fits your project.

Each package has a focused API. Check the README and source to see whether it fits your use case.

TYPESCRIPT · NPM

@dovocode/enum

Create type-safe enums compatible with TypeScript type stripping.

View on npm Source Code

TYPESCRIPT · NPM

thread-func

Create thread-safe function wrappers through a small API.

View on npm Source Code

TYPESCRIPT · NPM

ifty

A strongly typed if-pattern for conditional logic in TypeScript.

View on npm Source Code

Want to see more?

Check out my GitHub profile for more open-source projects and contributions

Visit GitHub Profile

06 / WHY OPEN SOURCE

Open ecosystems over lock-in.

Whenever practical, I prefer open standards, portable architectures, and systems that preserve choice. Open source is one practical way to share knowledge, expose decisions, and let useful work travel further.

Types are part of the design

Strong typing documents intent, prevents entire classes of bugs, and makes software easier to understand without hidden knowledge.

Small, clear APIs

A focused tool should do one job well. Simplicity makes adoption easier and long-term maintenance more realistic.

Documentation is part of the product

Useful software explains its purpose, constraints, and expected behavior. Documentation is how a tool scales beyond its author.

Leave the ecosystem better

Every contribution should improve the code, the explanation, the developer experience, or the path for the next contributor.

Users should retain ownership of their data and the freedom to migrate. Portability is not only an architectural preference; it protects long-term autonomy.

Start a conversation