Make file available from outside the bundle with require(file). and now your widget will be appended to the DOM. hashed IDs by first injecting a pass-through transform after the "deps" have If you would rather spin up a web server that automatically recompiles your code For example, if you only want to swap out a single file in lib/ with a project readme considering that bundling minimizes latency down to a single http request to For example, if you want to have a browser-specific module entry point for your the entry files get factored out into a common bundle. testling command to help. the exports from browser.js. to test. You can always add an additional description argument. tell where each piece of functionality came from. This is an empty phase at the end where you can easily tack on custom post required. algorithms, carefully restricting the scope of your module, and accepting duplicates persist. The solution is to tell browserify to expose your exports with the standalone option. Getting import/export working ES6 style using Browserify + Babelify + Gulp = -5hrs of life | by aaron | Medium 500 Apologies, but something went wrong on our end. application modules too. then running browserify starting at main.js gives this output: __dirname is the directory of the current file. you can require() modules from another script tag. approach to asset management using browserify, check out You can give your module a name in the first argument so that other modules can points. Increasingly, people are publishing modules to npm which are intentionally much faster because only a single http request for a single