How do I use wzrd with multiple entry points?

Specify mappings like 'wzrd app.js:bundle.js foo.js:bar.js' to bundle different files for different requests, allowing flexible output configurations for complex projects.

Does wzrd support hot module replacement?

No, wzrd only provides live reloading by re-bundling on changes. For hot module replacement, you'd need to look at other tools or extensions, as it's not built-in.

How to enable HTTPS in wzrd for local testing?

Use the '--https' flag when starting wzrd, which creates a server at https://localhost:4443 with a self-signed certificate, though browsers will show a security warning.

What's the difference between wzrd and beefy?

wzrd is inspired by beefy but aims for less 'magic', giving developers more direct control over Browserify arguments. Beefy might have more automated features, while wzrd is more transparent and minimal.

Can I pass custom arguments to browserify through wzrd?

Yes, use '--' followed by arguments, e.g., 'wzrd app.js -- -t brfs' passes '-t brfs' to browserify for applying transforms like brfs during bundling.

Is wzrd good for production deployment?

No, wzrd is strictly a development server. For production, you should build your bundles with browserify separately and use a robust server like Nginx or a cloud service.

How to handle client-side routing with wzrd?

Enable the '--pushstate' flag, and wzrd will serve index.html for all unmatched routes, allowing HTML5 pushstate routing in single-page apps without additional configuration.

wzrd — Minimal Browserify Dev Server

What is wzrd?

wzrd is a super minimal development server designed specifically for Browserify-based projects. It automatically bundles JavaScript files with Browserify and serves them locally during development, providing live reloading and essential features like HTTPS support and pushstate routing. It solves the problem of setting up a dedicated development environment for Browserify without complex configuration.

Target Audience

Frontend developers and Node.js developers who use Browserify for bundling and need a simple, lightweight local server for development with live reload capabilities.

Value Proposition

Developers choose wzrd for its minimalism and transparency—it offers just enough features to streamline Browserify development without hidden magic, making it easy to understand and control the bundling process.

Super minimal browserify development server

Use Cases

Best For

Quickly prototyping Browserify-based applications with live reload
Developing single-page applications that require HTML5 pushstate routing
Local development with HTTPS for testing secure contexts
Projects needing multiple entry points with custom output mappings
Minimalist development setups that avoid heavy build configurations
Learning Browserify workflows with a straightforward server

Not Ideal For

Projects using bundlers other than Browserify, such as Webpack or Vite
Development setups requiring hot module replacement for faster feedback loops
Teams needing integrated debugging tools or advanced build configurations out of the box
Applications with complex asset pipelines involving CSS, images, or other non-JavaScript resources

Pros & Cons

Pros

Live Browserify Bundling

Automatically bundles entry files with Browserify and serves them live, eliminating manual rebuilds during development, as highlighted by the simple command 'wzrd app.js'.

Minimal Configuration Overhead

Requires almost no setup; it generates an index.html if missing and serves files directly, making it ideal for quick prototyping without complex config files.

HTTPS Development Support

Includes a '--https' flag to start a local HTTPS server with a self-signed certificate, useful for testing secure contexts without external tools.

Pushstate Routing Enablement

With the '--pushstate' flag, it serves index.html for unmatched routes, facilitating HTML5 pushstate for single-page applications without extra server setup.

Cons

Browserify-Only Dependency

Tied exclusively to Browserify, so it's incompatible with other bundlers, limiting its use in projects that might switch or use multiple tools.

Missing Modern Dev Features

Lacks hot module replacement, source maps by default, and advanced debugging integrations, which are standard in more comprehensive development servers.

Setup Requires Dual Installation

Needs both wzrd and browserify installed separately (local or global), adding setup steps compared to all-in-one solutions that bundle the bundler.

Frequently Asked Questions

What is wzrd?

Target Audience

Frontend developers and Node.js developers who use Browserify for bundling and need a simple, lightweight local server for development with live reload capabilities.

Value Proposition

Use Cases

Best For

Quickly prototyping Browserify-based applications with live reload
Developing single-page applications that require HTML5 pushstate routing
Local development with HTTPS for testing secure contexts
Projects needing multiple entry points with custom output mappings
Minimalist development setups that avoid heavy build configurations
Learning Browserify workflows with a straightforward server

Not Ideal For

Projects using bundlers other than Browserify, such as Webpack or Vite
Development setups requiring hot module replacement for faster feedback loops
Teams needing integrated debugging tools or advanced build configurations out of the box
Applications with complex asset pipelines involving CSS, images, or other non-JavaScript resources

Pros & Cons

Pros

Live Browserify Bundling

Automatically bundles entry files with Browserify and serves them live, eliminating manual rebuilds during development, as highlighted by the simple command 'wzrd app.js'.

Minimal Configuration Overhead

Requires almost no setup; it generates an index.html if missing and serves files directly, making it ideal for quick prototyping without complex config files.

HTTPS Development Support

Includes a '--https' flag to start a local HTTPS server with a self-signed certificate, useful for testing secure contexts without external tools.

Pushstate Routing Enablement

With the '--pushstate' flag, it serves index.html for unmatched routes, facilitating HTML5 pushstate for single-page applications without extra server setup.

Cons

Browserify-Only Dependency

Tied exclusively to Browserify, so it's incompatible with other bundlers, limiting its use in projects that might switch or use multiple tools.

Missing Modern Dev Features

Lacks hot module replacement, source maps by default, and advanced debugging integrations, which are standard in more comprehensive development servers.

Setup Requires Dual Installation

Needs both wzrd and browserify installed separately (local or global), adding setup steps compared to all-in-one solutions that bundle the bundler.

Frequently Asked Questions

wzrd

What is wzrd?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

wzrd

What is wzrd?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?