Over five years of work experience across three jobs, I’ve developed and maintained frontend CLI tools at every single one of them. While monitoring and alerting for frontend pages and server-side applications is taken for granted, these tools need it too. This article covers everything from error handling to reporting and troubleshooting.

Some thoughts and takeaways from building a private deployment system.

How to integrate a commonly used bash script into the npm ecosystem, demonstrated with a recent CR (Code Review) submission script.

A guide to batch-migrating npm packages from one npm registry to another.

I recently took over the frontend team’s service stability governance and encountered some very distinctive production issues. Here I’ll document one particularly “interesting” bug hunt.

Our team recently migrated two projects to degg 2.0, and both exhibited serious memory leak issues. Here I’ll use the tracking service I maintain as an example for debugging. After going live, memory growth looked like the chart below—the red box marks the degg 2.0 production runtime window. Within just 36 hours, memory had grown to 50%, while it normally stabilized at 20%-30%, clearly indicating a memory leak.

Life without a mock service is unbearable.

Testing your Node.js applications with Jest

Refactoring the company’s legacy JSP project by introducing a Node.js layer.

Frontend developers picking up Node.js still need to brush up on some server-side knowledge.