mattdesl/budo

Support arbitrary middleware

Open

#91 opened on Oct 14, 2015

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (124 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (2,174 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Was playing around with budo-less and had the idea that budo could support any arbitrary middleware that followed a particular pattern (maybe like simple-less-middlewares), and would map that to a cli switch when budo is invoked.

I imagine budo doesn't want to get bogged down with heavy, convoluted configuration (see: webpack compared to browserify itself), but I could also see a usecase for two to three middlewares being all that's necessary to have a full-fledged dev server running within minutes without a ton of task runner or watcher configuration (see: gulp), etc.

Contributor guide

Research direction
Examine the existing middleware pattern in budo and propose a generic middleware interface that allows loading any middleware via CLI flags.
Tech stack
javascript
Domain
developer experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.jsHTTP middleware concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70