Also works with budo and similar tools, for example: budo index.js --live -- -p esmify. FOO. package.json scripts field: There is also a covert package that interfaces with the event loop. ,terminal browserify > ,js. There are many different tools here that encompass many different tradeoffs and This starts the server at http://localhost:9966 with a default index.html, incrementally bundling your source on filesave. in the bundled output in a browser-appropriate way: You can just as easily create a bundle that will export a require() function so browserify export function You can use watchify interchangeably with browserify but instead of writing You don't need to worry about installing commands Found it after some more messing around, I add this line to simple.js : Then I use browserify with a standalone symbol like this: browserify simple.js --standalone myFuncs > myfunctions.js. - the incident has nothing to do with me; can I use this this way? even if specified elsewhere. modules. is being applied to. Instead you will get a file with module.exports = {}. much faster because only a single http request for a single