A client-side CommonJS `require` implementation that does NOT require a precompilation build step nor server-side middleware. It instead utilizes synchronous `XMLHttpRequest`s and `eval` instead, which does impose a series of limitations unless you're willing to generate a whole mess of `404`s. Terrible for performance, nice for dynamic ease of use.
Want to see pretty graphs? Log in now!
npm install breq
|5||downloads in the last month|
|Last Published By|
|Version||0.2.0 last updated 5 months ago|
|Keywords||browser, require, commonjs, browser-require|
"breq" (browser-require) is a client-side CommonJS
require implementation that does NOT require a
precompilation build step nor server-side middleware. It instead utilizes synchronous
eval instead, which does impose a series of limitations
unless you're willing to generate a whole mess of
Terrible for performance, nice for dynamic ease of use.
In your web page:
<script src="dist/breq.min.js"></script> <script> var mod = require("./someCjsModule.js"); </script>
Given the browser-based nature of "breq", there are some important limitations to keep in mind that
differ from Node's
require.resolve lookup algorithms:
- It only works over HTTP and HTTPS due to browser security settings for
- It does NOT do any actual "lookups", it only resolves the exact relative path provided.
- It currently only supports paths that start with one of the following patterns:
- It does not support the "any depth"
node_modulesdynamic lookup for named modules as this would usually result in a series of
404s before it is located.
- It does not attempt to append the ".js" extension, etc. to the path provided. As this is made for the web, URI paths are critical and some users will need to consume scripts that do not end with the ".js" extension.
- It does not support loading CoffeeScript modules.
- It does not currently support loading JSON "modules".
Some ideas for future exploration in "breq":
- Add support for JSON "modules".
- Add a configuration object.
Allow consumers to configure a "module root" [with either a method like
setModuleRootor a config property like
require.paths] where we can seek out named modules, e.g.
require.setModuleRoot("/node_modules/"); var mod = require("myCjsModule"); // path will [first] resolve to "/node_modules/myCjsModule/index.js"
Allow consumers to set a configuration option that does enable the actual Node-style lookup algorithm, keeping in mind that this setup will likely produce an exceptionally large quantity of
404s. This would also include auto-appending the ".js" extension during some of the lookup attempts if it is not already present, e.g.
var mod = require("./myCjsModule"); // path will resolve to "./myCjsModule.js"