Part 07 · About the author
Hi, I'm Nilay.
every fix here was run before it was written up.
I'm Nilay, a developer. I build web apps, tools and small products, and I foundedPaisaTools, a set of free money calculators. This notebook covers the errors developers are searching for right now, mostly in Node, npm, TypeScript, Python and AI SDKs: what the error really means, the fix that works, and the exact versions it was checked on.
The site is nilaykabariya.blog, and people refer to it by every name it has picked up: Nilay Kabariya, nilaykabariya, Nilay's Notebook, the Nilay blog, or just {nk}, the mark in the corner of every page. They're all this one notebook.
Why this exists
When a new release breaks a build, the first search results are usually forum threads full of guesses, or answers written for an older version. What I wanted was one page that shows the exact error, proves which fix works on the versions people actually have today, and says which popular suggestions don't. That's what each post tries to be. New releases (Node, npm, TypeScript, Python, Prisma, AI SDKs) get tested on the day they ship, because that's when people need the answer.
How every post is made
The fixes are tested on real machines and CI, the posts are drafted with AI assistance, and they're published by me. In practice:
- Reproduced first. Each error is triggered for real in a clean project, on a Windows 11 PC or on GitHub Actions runners (Linux, Windows, Docker images), with the exact versions listed at the top of the post. If it can't be reproduced, it doesn't get a post.
- The fix is verified. The fix is applied and the project is run again to confirm it works. A fix that wasn't run is labelled as untested, or left out.
- Real output, not paraphrase. Error messages, commands and numbers are copied from the actual run. Only personal paths are shortened.
- Failures stay in. Fixes that people suggest but that didn't work are listed too, with what they printed.
- The scripts are public. The test projects and their output are in the nk-repro repository on GitHub (every folder, its posts and its latest run are listed in the repro log), and most posts link the exact folder, so you can run the same test yourself.
- Dated. Every post shows when it was tested. When a new version changes the answer, the post is re-tested and its date changes to "Updated".
Independence
No company pays for a verdict here. If the site shows ads, they're kept apart from the content and never decide what gets tested or what a post concludes. If a post ever contains an affiliate link or a sponsored product, it will say so at the top of the post, before the first link. The details are on the Disclaimer page.
Corrections
Tools change fast and things here will sometimes be wrong. If a fix didn't work for you, open an issue on thenk-repro repository with the post's address, your operating system, the versions and the error, or emailhello@nilaykabariya.blog. The test is run again, and if the post is wrong it's corrected and its date changes to "Updated".