browser-pack

browser-pack copied to clipboard

Add ability to expose require() with standalone.

4

Designed to fix #45. This sets up the ability to opt-in to exposing a `require()` when bundling in standalone mode, like this: ``` js browserify({standalone: 'whatever'}) .require('entry', {expose: 'whatever'}); ```...

jmm

Not able to use standalone & require flags at the same time

11

As notified at https://github.com/substack/node-browserify/issues/939, I'm not able to generate a bundle that at the same time can be used standalone and also export its content so it can be required...

piranna

This allows you to identify the id of the current file, in turn accessing that file's cached require values. This makes it possible, with a few extra steps, to override...

hughsk

If opts.standalone === true, then the standalone name will be set to the filename (without extension) of the source file. Addresses issue #42.

sethmcl

When running with `opts.standalone`, I would like the standalone name to be dynamic, based on the source file being packed. For example, if the source file is `/lib/alert.js`, the standalone...

sethmcl