Plugin for the Lasso.js that adds support for transporting Node.js-style modules to the browser.
This plugin is included as part of the lasso module so it is not necessary to use npm install to add the module to your project. However, if you want to use a specific version of the lasso-require plugin then you can install it using the following command:
npm install lasso-require --save
This plugin is enabled by default, but if you want to provide your own configuration then you can do that using code similar to the following:
require('lasso').configure({
require: {
extensions: ['.js'], // Defaults to ['.js']
transforms: [ // Browserify compatible transforms
'deamdify'
]
}
})The lasso-require plugin introduces two new dependency types that you can use to target Node.js modules for the browser. There usage is shown in the following browser.json file:
{
"dependencies": [
"require: jquery",
"require-run: ./main"
]
}These new dependency types are described in more detail below.
The require dependency type will wrap a Node.js module for delivery to the browser and allow it to be required from another module. For example:
Input modules:
foo.js:
exports.add = function(a, b) {
return a + b;
}bar.js:
var foo = require('./foo');
exports.sayHello = function() {
console.log('Hello World! 2+2=' + foo.add(2, 2));
};Output Bundles:
After running the following command:
lasso require:./foo require:./bar --name testThe output written to static/test.js will be the following:
$_mod.def("/foo", function(require, exports, module, __filename, __dirname) { exports.add = function(a, b) {
return a + b;
} });
$_mod.def("/bar", function(require, exports, module, __filename, __dirname) { var foo = require('./foo');
exports.sayHello = function() {
console.log('Hello World! 2+2=' + foo.add(2, 2));
}; });NOTE: $_mod is a global introduced by the client-side Node.js module loader. It should never be used directly!. The code that declares $_mod is not shown in the output above for brevity.
In the previous examples, neither the foo.js or bar.js module will actually run. The require-run dependency type should be used to make a module self-executing. This is the equivalent of the entry point for your application when loaded in the browser.
Continuing with the previous example:
Input modules:
foo.js (see above)
bar.js (see above)
main.js:
require('./bar').sayHello();Output Bundles:
After running the following command:
lasso require-run:./main --name testAlternatively:
lasso --main main.js --name testThe output written to static/test.js will be the following:
$_mod.def("/foo", function(require, exports, module, __filename, __dirname) { exports.add = function(a, b) {
return a + b;
} });
$_mod.def("/bar", function(require, exports, module, __filename, __dirname) { var foo = require('./foo');
exports.sayHello = function() {
console.log('Hello World! 2+2=' + foo.add(2, 2));
}; });
$_mod.run("/main", function(require, exports, module, __filename, __dirname) { require('./bar').sayHello(); });The lasso-require supports the package.json browser field for remapping a JavaScript module to a different module during client-side bundling. For example:
{
"browser": {
"./foo.js": "./foo-browser.js"
}
}The lasso-require plugin also allows modules to be conditionally remapped based on the set of enabled flags by adding additional information an browser.json in the same directory as a module. For example:
{
"dependencies": [
...
],
"requireRemap": [
{
"from": "./foo.js",
"to": "./foo-mobile.js",
"if-flag": "mobile"
}
]
}If the mobile flag is set during optimization and the foo.js module is required on the client (e.g., require('./foo')) then the returned module will be the exports for foo-mobile.js (not foo.js).
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent