With big fanfare, Daniel Roe, the inventor and person in charge of Nuxt, proudly released the newest version of my favourite JavaScript framework on March 7, 2025: Nuxt v3.16. It promised better performance, better error handling, and a lot more. The full announcement blog post showed that all Nuxt contributors are proud of the new version. They also gave instructions on how to upgrade to v3.16 from previous versions—which immediately broke my Tailwind styling. However, thanks to the Nuxt community, I can now show you the easy fix to this problem.
Category: JavaScript & Typescript
Specific problems and their solutions for JavaScript/Typescript-related topics.
-
Nuxt v3.16 is out—and TailwindCSS doesn’t seem to like it and breaks styling after upgrade. Here’s how you can fix it
-
![Nuxt v3 Error: “ERROR [unhandledRejection] Nuxt instance is unavailable!”](https://blog.kolja-nolte.com/wp-content/uploads/nuxt-v3-825x510.webp "Read \"Nuxt v3 Error: \"ERROR [unhandledRejection] Nuxt instance is unavailable!\"\"")
Nuxt v3 Error: “ERROR [unhandledRejection] Nuxt instance is unavailable!”
Another day, another Nuxt project. Nuxt has just released
v3.14.1592, which I chose because I wanted to have a look at the unannounced Nuxtv4, which uses TailwindCSSv4and other packages with major changes.So I ran the usual single-line command line to install Nuxt from scratch and I’m ready to explore—or so I had thought.
(more…) -
Quick fix for “ExperimentalWarning: CommonJS module using require()” error message in Node.js
JavaScript frameworks and meta-frameworks such as Next.js or Nuxt.js are everywhere. Working with them locally is astonishingly easy; all you need is Node.js and a package manager.
If you’re using the latest version of Node.js, chances are good that you’ve run into the same bug as I have, and it appeared whenever I launched the development server: “ExperimentalWarning: CommonJS module using require().” Here’s the reason why it pops up and two ways to fix it.
(more…)
