Search for a command to run...
NextJS React app startup process goes from 20s to just 3
Senior Full Stack Developer in the ☁️
Creator of supereffective.gg, a Pokémon community running on Next.js and @vercel
No comments yet. Be the first to comment.
Articles about frontend and backend developemnt in JavaScript, TypeScript, NodeJS, ReactJS, ExpressJS, Babel, NextJS, etc...
For people that are new to monorepos like me, there are a lot of struggles that you will face and no one talks about them in the articles you can find out there, especially when it comes to monorepos with NextJS apps. Setup a monorepo with NPM or Yar...
In this case, using the scroll event offers more flexibility than using the IntersectionObserver API
Feeling the web developer fatigue? You are not alone!
The IntersectionObserver is a powerful API for tracking elements' visibility within the viewport. Many modern web applications use it to implement lazy loading, infinite scrolling, or other interactions that depend on an element's visibility. When it...
The addon system has been completely rewritten, so now you can also provide your own or turn off default ones. The UI also looks much better, especially on mobile. The styles have been reworked so the look and feel are more similar to StoryBook's UI....
Lightweight drop-in app for rapid React component development and visualisation
If you are a software engineer that uses Docker containers on your macOS for development, you might have experienced how slow can they get sometimes, especially when they start up or with I/O intensive operations like installing dependencies.
Since macOS Big Sur, there is a new Virtualization Framework that software like Docker can use to access the computer resources more effectively. This, when combined with the new VirtioFS introduced in macOS Monterey 12.2 will make your containers fly like never before.
I especially notice the difference when starting my NextJS apps (it went from ~20 secs to ~3) or when installing dependencies (time is drastically better here).
With 3 NextJS apps running, I can see how much better my resources are used:
CPU (Idle containers: 3 - 5 %)
Allocated Memory (8.02 GB of the maximum configured for Docker, 8.00 GB)
Before this, Docker was using qemu and it was eating a lot of memory (more than the limit I configured).
All you need to do, if you have macOS 12.2 or greater, is to enable these experimental features in your Docker for Mac settings, and restart it:
