How Odd 0 ▲ niqwithq 13 minutes ago · Tech · hide The other day, I've noticed something odd. I wanted to start my local Next.js application, but when I opened up the browser—as I usually do—I was informed that it wouldn't let me run my application, if I didn't upgrade it first. That wasn't the odd part yet (although this seemed a little odd). The odd part was that when Next.js informed me about this, it also informed about how to upgrade and it didn't just show an npm command as one might have expected. Instead it showed me a prompt that I could use in order to upgrade. OK, hold on! Let me break down for a second what is happening here. Upgrading a Next.js application is a well-known and well-documented process. Usually, when I want to upgrade it, I run the following command (forgive me if it gets a bit technical here. But I have to use this brief example to illustrate a point): npm install next@latest This is a single commands that I run in my terminal this is telling my package manager clear instructions on what to do. Now what's… Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town