Browserbuild allows you to write code for the browser that leverages
exports, but that gets exposed as a global.
Browserbuild solves the same problem everyone wants to solve: how do I make a module interoperable between the server and client?
It takes 3 easy steps
/*** Module dependencies.*/var a = require'./b'/*** Module exports.*/;
$ browserbuild world.js# outputs dist/world.js
On the server-side:
On the client side:
undefinedtype checking for
require.async, no CommonJS transport proposals.
requireimplementations on the client.
_. Just like everyone is used to.
requirefunctions by Jonah Fox, with modifications by TJ Holowaychuk <email@example.com>
(The MIT License)
Copyright (c) 2011 Guillermo Rauch <firstname.lastname@example.org>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.