explaingit

insin/nwb

★ 5,544JavaScriptAudience · developerComplexity · 2/5Setup · easy

TLDR

A deprecated zero-config toolkit for building React, Preact, and plain JavaScript apps and libraries. The author now recommends Vite, which does the same job and is actively maintained.

Mindmap

mindmap
  root((nwb))
    What it does
      Zero-config builds
      Dev server with hot reload
      Test runner included
    Supported frameworks
      React
      Preact
      Inferno
      Plain JavaScript
    Tech Stack
      JavaScript
      Webpack
      Babel
      Node.js
    Status
      Deprecated
      Migrate to Vite
    Audience
      JavaScript developers
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Reference the nwb source to understand how zero-config JavaScript toolkits wrapped Webpack and Babel before Vite existed.

USE CASE 2

Migrate an existing nwb-based project to Vite by reviewing the feature mapping the author describes.

USE CASE 3

Use as a historical example of a pre-Vite build tool when researching JavaScript tooling evolution.

Tech stack

JavaScriptWebpackBabelNode.js

Getting it running

Difficulty · easy Time to first run · 5min

Project is deprecated, no new setup recommended. Migrate to Vite instead.

No explicit license information provided in the explanation.

In plain English

nwb was a toolkit for building JavaScript web applications and libraries without needing to configure the underlying build tools yourself. It handled the setup for React, Preact, Inferno, and plain JavaScript projects, wrapping tools like Webpack and Babel so developers could start coding immediately rather than spending time on build configuration. The README opens with a clear deprecation notice: nwb is no longer maintained, and the author recommends using Vite instead. The project was built during a period when JavaScript tooling was fragmented and setting up a working development environment required manually coordinating many separate packages. nwb solved that by providing a single command-line tool that handled local development servers, testing, and production builds out of the box. While it was active, nwb could scaffold new projects with one command and gave you hot reloading during development, a test runner, and optimized production builds with no initial configuration file required. If you needed to adjust settings for your project, it exposed a smaller configuration surface than the underlying tools. It also supported publishing npm packages in multiple module formats for compatibility across environments. The author's note explains that Vite now does what nwb set out to do, is actively maintained, has a large ecosystem of plugins, and serves as the foundation for several popular frameworks. Anyone with a project that still uses nwb is encouraged to migrate. This repository remains public for reference but receives no further updates.

Copy-paste prompts

Prompt 1
I have an old project using nwb and I want to migrate it to Vite. What steps should I follow to replace nwb with Vite for a React project?
Prompt 2
Show me how nwb configured Webpack and Babel under the hood so I understand what Vite replaced when nwb was deprecated.
Prompt 3
What Vite plugins or configuration options replace the features nwb provided for building and publishing npm packages in multiple module formats?
Open on GitHub → Explain another repo

← insin on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.