TypeScript semver detector

A personal response to a developer problem

I created ts-semver-detector before an AI-assisted solution existed for the version-suggestion problem I was exploring at Microsoft. The public project was a way to make similar benefits available to other developers, without making it part of the Microsoft implementation.

Static analysis, not runtime AI

The CLI uses TypeScript compiler APIs to inspect exported declarations in old and new .d.ts files. Rules compare interfaces, types, functions, classes, and other declarations, then produce change reports and a suggested major, minor, or patch increment. The suggestions are not a proof of complete behavioral compatibility.

A separate path from the Microsoft feature

For the Microsoft workflow, an AI-assisted approach was the better fit. I owned that feature from design through implementation, testing, and validation. This public CLI remained a separate personal project: it did not go into production and is still a work in progress.

What the experiment taught me

The project helped me learn to use AI effectively when writing larger codebases, alongside the static-analysis work itself. AI assistance was part of my development process; the public tool makes its version recommendations through compiler analysis and rules.