
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
watchify-server
Advanced tools
This is a bare-bones development server for watchify. For a more feature-rich development server built on the same underlying modules, see budo.
Features at a glance:
9966 or the next available portstdout with ndjsonnpm install watchify-server [-g|--save]
Example with CLI:
watchify-server index.js --port 8000 --dir public/
It might look like this with npm scripts and garnish for pretty-printing:
"devDependencies": {
"watchify-server": "^1.0.0",
"garnish": "^2.3.0"
},
"scripts": {
"start": "watchify-server src/app.js --port 8000 --dir public | garnish"
}
Typically this module is used via a CLI, but it also exposes a simple JavaScript API.
Usage:
watchify-server entry.js [options] -- [browserify]
Options:
--port, -p port to listen on, default 9966
--host, -h host to listen on, default localhost
--dir, -d directory for static content, default process.cwd()
--no-debug turns off source maps
--no-error-handler turns off syntax error handling
--index optional file path to override default index.html
--title title of HTML index
--css, -s optional style sheet href, relative to --dir
Browserify options are passed after the -- full stop.
The --title and --css arguments are only applicable to the default index.html handler.
Note: The API does not set any default config on the browserify instance, so it is up to the developer to set debug, packageCache, and cache.
server = watchifyServer(browserify, opt, [cb])Creates a new watchify server that wraps the specified browserify instance. Options:
entry (required) the path to the entry file to browserifysilent set to true to disable logsOther options are passed to watchify-middleware and serves, but defaults port to 9966 and errorHandler to true.
The returned server emits 'update' events from watchify-middleware.
The callback takes the form callback(err, ev) with the following event parameters when the server starts listening:
{
url: String // 'http://localhost:8080/'
port: Number // 8080
host: String // 'localhost'
}
server = watchifyServer.fromArgs(browserifyArgs, [opt], [cb])Creates a new watchify server from the given command-line browserify args array, with optional opt overrides and a callback.
The entry is resolved by browserify arg parsing, so opt is optional and cb can be passed as the second parameter.
index handlerMIT, see LICENSE.md for details.
FAQs
a bare-bones development server for watchify
We found that watchify-server demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.