Sorting out images in Webpack is not too bad up to a point. The url-loader + file-loader combination is usually enough to satisfy needs. However, when you have too many require() for large images, it can take up to 20s or longer to hot-reload after a compile…
Here’s how to mitigate the situation.
Continue reading
In terminal:
$ lsof -t -i tcp:80 | xargs killIf 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 task 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 readingEven if Edge is not called Internet Explorer, it’s still basically IE. 🙁 And IEs don’t support scrollTo.
Continue readingEither use background image, or the fancy new object-fit on <img> tags, which works almost exactly the same as background image:
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 reading