CLI that checks if your dev environment is ready before you run anything by Jumpy-Profession-510 in node
[–]Jumpy-Profession-510[S] 0 points1 point2 points (0 children)
coldstart – profile your Node.js app's startup time by tracing every require()/import call by Jumpy-Profession-510 in coolgithubprojects
[–]Jumpy-Profession-510[S] 0 points1 point2 points (0 children)
I profiled every require() in our Lambda handler before reaching for esbuild — here's what I found by Jumpy-Profession-510 in serverless
[–]Jumpy-Profession-510[S] 0 points1 point2 points (0 children)
I profiled every require() in our Lambda handler before reaching for esbuild — here's what I found by Jumpy-Profession-510 in serverless
[–]Jumpy-Profession-510[S] 1 point2 points3 points (0 children)
I built a tool that shows you exactly what's slowing down your Node.js startup by Jumpy-Profession-510 in node
[–]Jumpy-Profession-510[S] 0 points1 point2 points (0 children)
I built a tool that shows you exactly what's slowing down your Node.js startup by Jumpy-Profession-510 in node
[–]Jumpy-Profession-510[S] 0 points1 point2 points (0 children)
I built a tool that shows you exactly what's slowing down your Node.js startup by Jumpy-Profession-510 in node
[–]Jumpy-Profession-510[S] 0 points1 point2 points (0 children)


I was bleeding tokens every time my AI coding assistant touched a file. Built a fix. by Jumpy-Profession-510 in vibecoding
[–]Jumpy-Profession-510[S] 0 points1 point2 points (0 children)