Way to enforce the standalone package name

If a module is named like `peaks.js`, where the `.` has a decorative value and not a namespace value, `/standalone/peaks.js` is equivalent to the `--standalone peaks.js` browserify command.

The issue is the exported module is exported as `window.peaks.js`, `js` becoming a property of the namespace `peaks`.

It does not seem to be doable in substack/node-browserify#818: what could be a proper way to define the standalone module name for browserify-cdn?

I would definitely map `/standalone/peaks.js` as `--standalone peaks`, to match the library examples and so on.

Thanks for your insights :-)

The issue names no files or tests; start by tracing how the /standalone/ URL is handled and how browserify receives the --standalone value. Review the limitation discussed in substack/node-browserify#818. Done means /standalone/peaks.js produces a global named peaks rather than window.peaks.js.

Written by the indexing model from the issue text.