Simple node script to pre-render react components using AMD modules (commonjs support coming soon). This is designed to be used as a tool in the build process and can run right after Grunt/Gulp or any other build tools you use.
Any application rendering their UI from javascript should pre-render it's UI because of the improved SEO and UX it offers, not just apps with a server component. This script will attempt to pre-render your React components in node and inject them into your html as part of your build task and focuses on providing helpers for AMD module support. The most difficult part of this process is requiring AMD components in node. This script aims to help by allowing you to pass in a simple package configuration, so node knows how to find those modules, a list of patterns/modules to ignore, for plugins and hosted modules, props, export names for babel generated AMD modules, and more. Please refer to Options for a full list.
- Currently only supporting React >
0.14.0. - Your components render functions cannot use any modules that are not local or are required via requirejs plugins. This script will need to reroute requires for any file that is not local to a file that is (to prevent module not found errors) If any of the modules that are remapped are used in your render function, it may cause errors. See Remap.
- Common JS support coming soon.
Below is a full example using most of the available options. This configuration is for the project in samples/amd
var amdDir = path.join(__dirname, '../samples/amd');
var target = path.join(amdDir, 'index.html');
var component = 'js/layout/App';
var mount = 'body';
var exports = 'App';
var requirejs = {
baseUrl: amdDir,
paths: {
'js': 'js',
'vendor': 'vendor',
'react': 'vendor/react/react.min',
'react-motion': 'vendor/react-motion/build/react-motion',
'babel-polyfill': 'vendor/babel-polyfill/browser-polyfill'
},
map: {
moduleRoot: path.join(amdDir, 'js'),
remapModule: 'js/config',
ignorePatterns: [/esri\//]
}
};
reactPrerender({
target: target,
component: component,
mount: mount,
exportName: exports,
requirejs: requirejs
});Here is another example for the same project that leverages a build profile instead of providing a baseUrl and paths object.
var amdDir = path.join(__dirname, '../samples/amd');
var target = path.join(amdDir, 'index.html');
var component = 'js/layout/App';
var mount = 'body';
var exports = 'App';
var requirejs = {
buildProfile: path.join(amdDir, '../build.js'),
map: {
moduleRoot: path.join(amdDir, 'js'),
remapModule: 'js/config',
ignorePatterns: [/esri\//]
}
};
reactPrerender({
target: target,
component: component,
mount: mount,
exportName: exports,
requirejs: requirejs
});This script exports a single function that takes an options object with the following options.
Type: string
Default: none
Required: Yes
Path to your html file that you are appending your react component into.
Type: string
Default: none
Required: Yes
Path to your component. If using amd, this would be relative to your baseUrl.
Type: string
Default: none
Required: Yes
Query string used to locate the dom node that react renders to. For example, something like body, #root, or .react-mount. Make sure it only matches a single node otherwise the script may inject your component into each match.
Type: object
Default: {}
Required: No
Default props for your component.
Type: string
Default: default
Required: No
If you are using es6 and compiled to AMD, this is the export name of the module if it is not the default export. For example, if your component class looks like this:
export class App extends React.Component { ... }Then your exportName would be App. If it's a default export then you do not need to provide this.
Type: object
Default: none
Required: No
If you are using AMD, you will need to include this configuration with some of the options listed below.
Type: object
Default: none
Required: No
This is your paths/package configuration with the paths relative to your baseUrl. For Example:
{
'js': 'js',
'vendor': 'vendor',
'react': 'vendor/react/react.min',
'react-motion': 'vendor/react-motion/build/react-motion',
'babel-polyfill': 'vendor/babel-polyfill/browser-polyfill'
}Type: string
Default: none
Required: No
Base Url for your paths/packages object provided above.
Type: string
Default: none
Required: No
Full Path to a build profile for requirejs's optimizer (not relative to your baseUrl). This can be an alternative to path's and baseUrl since it will read the path's and baseUrl from the profile. See samples/build.js for an example.
If you have require calls to modules that are not local or use plugins, such as text!template/header.html then you may need to use the following three options to prevent requirejs from throwing a module not found error. This is achieved by creating a map object based on dependencies starting at the moduleRoot that reroutes all require calls to files matching ignorePatterns to the remapModule instead.
Type: string
Default: none
Required: No
Full path to your entry module (not relative to your baseUrl). This plugin will attempt to create a dependency tree starting from here so that it can locate paths it needs to ignore.
Type: string
Default: none
Required: No
Relative path to the component you want to remap your :empty modules or plugins to. As stated above, this should not use plugins, cdn modules, or any modules that require these empty modules. Typically I use a config module that has no dependencies except for a possible constants file.
Type: string|regexp|array[string|regexp]
Default: none
Required: No
Patterns to match modules that should be ignored and included in the map. Paths that match this pattern will be remapped to the above remapModule. This options accepts a string, RegExp, an array of strings, or an array of RegExp's.
If you are interested in contributing, please fork the develop branch. That is the branch with the latest changes in it and will be the most up to date. No code will be merged unless the current tests pass, including linting. Add documentation if you are adding a new feature and add tests where needed. When you are ready to merge your code, submit a pull request to the develop branch.