Sebastien Chopin
May 31 · 2 min read

Or how we changed the developer experience to stop switching between the terminal and browser.

Nuxt.js is a Vue.js framework to create different kind of web applications: Universal, Single Page, PWA or Static Generated.

ℹ️ These features are all available with v2.8.0 release.

Problems

  1. Developing JavaScript applications with Webpack or any bundler requires to switch between your browser and terminal for debugging purpose.
  2. Using console.log to debug when the app is server rendered requires to remember that logs will be displayed on the terminal when refreshing the page.

Solutions

Forwarding Webpack build state right in the browser and display them in a fancy manner.

Nuxt.js loading screen on startup

Same for Hot Module Replacement (really useful when the project gets bigger and takes more time to re-build).

Nuxt.js building indicator (hot module replacement)

Forwarding SSR logs to the browser in development mode

Forwarding and grouping SSR logs on refresh

NuxtJS Vision

The purpose to these changes is to use the terminal for commands only.

Now you can focus right on your code and its visual result 🙂

Be lazy, be smart, be Nuxt.

Links:

Sebastien Chopin

Written by

Writing JavaScript. Author of Nuxt.js.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade