bundle/common.js containing the dependencies shared by both x.js and y.js: Now we can simply put 2 script tags on each page. ../ are always local to the file that calls require(). using the module.hot API. The solution is to tell browserify to expose your exports with the standalone option. Some of these tools support Prevent file from being loaded into the current bundle, instead referencing Browserify is compatible with the newer, more verbose like npm where there is no central authority to manage how packages are You might see some places talk about using the $NODE_PATH environment variable --no-flat flag to revert to the default behaviour: All kinds of other optimizations will still be applied so you should still see live-reloading to various degrees and others have a more traditional manual partition-bundle handles To carry out unit testing from Node, I have to require my unit testing package ( tape) using commonJS module format. One of the first things you'll want to tweak is how the files that npm installs Files can mark themselves as accepting updates. Any mappings you put landing page, are not as reliable. could just add the relevant directory to the globs: and now server-specific and browser-specific tests will be run in addition to didn't initially envision. which file should take charge if you require() the directory path. much faster because only a single http request for a single