In terminal:
$ lsof -t -i tcp:80 | xargs killNodeJS: How to Find Memory Leaks
If you use NodeJS on your Backend, you have probably run into memory problems at one point or another. Compared to other systems where a child process is created and terminated with every request, Node is initiated only once, long-running, and particularly unforgiving in any tasks that leaves residue behind.
This post is an attempt at explaining how to dive into the seeming mess of memory lane and come up with insights, or better yet, solutions.
Continue readingnew Date() Not Valid in Safari
Not all the date formats can be used to create a date with new Date().
Turkish Characters show up as Gibberish in Chrome
Weird bug that only seems to bug Chrome:
Continue readingObject doesn’t support property or method ‘scrollTo’
Even if Edge is not called Internet Explorer, it’s still basically IE. 🙁 And IEs don’t support scrollTo.
Continue readingMaintain Image Width:Height Ratio
Either use background image, or the fancy new object-fit on <img> tags, which works almost exactly the same as background image:
Test Localhost on a Public URL
Sometimes we need to test localhost out on a public URL, for various reasons. We can do that with ngrok, which is a service that projects localhost ports onto a generated public URL.
Continue readingParallels Breaking Wacom
If your Wacom tablet stopped working after you installed Parallels.
Continue readingHow to Configure Sub-Routes in NextJS
For sub-routes like guides/post-slug to work, 3 pieces need to be in place: