问题
I'm using SpineJS (which exports a commonjs module) and it needs to be available globally because I use it everywhere, but It seems like I have to do Spine = require('spine')
on every file that uses Spine for things to work.
Is there any way to define Spine
once to make it globally available?
PS: I'm using Spine as an example, but I'm in general wondering about how to do this with any other library.
回答1:
Writing Spine = require('spine')
in each file is the right way to do.
Yet, there are several possibilities by using the global
or window
object (browserify sets the global
object to window
, which is the global namespace):
- in spine.js:
global.Spine = module.exports
- in any other .js file bundled by browserify:
global.Spine = require('spine')
- in a script tag or an .js file referenced by the .html file, after the spine.js file:
window.Spine = require('spine')
回答2:
First of all, for your example David is correct. Include all dependencies in every module you need it in. It's very verbose, but there is no compile time magic going on which alleviates all sorts of anti patterns and potential future problems.
The real answer.
This isn't always practical. Browserify accepts an option called insertGlobalVars
. On build, each streamed file is scanned for identifiers matching the key names provided and wraps the module in an IIFE containing arguments that resolve each identifier that is not assigned within the module. This all happens before the dependency tree is finalized, which allows you to use require to resolve a dependency.
TLDR
Use insertGlobalVars
option in Browserify.
browserify({
insertGlobalVars: {
spine: function(file, dir) {
return 'require("spine")';
}
}
});
For every file scanned, if an identifier spine
exists that's not assigned, resolve as require("spine")
.
来源:https://stackoverflow.com/questions/23480336/defining-global-variable-for-browserify