metalsmith-react-templates
A templating plugin using React.js templates

About
metalsmith-react-templates
is a metalsmith plugin to render files using React based templates.
Change Notice
As of v3.0.0
, this plugin will only use babel
as it's transpiler as react-tools
will be deprecated from 0.14
onwards. Read more about this at React's blog: Deprecating JSTransform and react-tools
As of babel 6
, additional plugin packages are needed for it to run. I've added the basic as peer dependency.
Installation
npm install metalsmith-react-templates
CLI Usage
Install the node modules and then add the metalsmith-react-templates
key to your metalsmith.json
plugins. The simplest use case just requires the template engine you want to use:
{
"plugins": {
"metalsmith-react-templates": true
}
}
If you want to specify additional options, pass an object:
{
"plugins": {
"metalsmith-react-templates": {
"baseFile": "base.html",
"isStatic": true,
"directory": "templates"
}
}
}
JavaScript Usage
Simplest use case:
var templates = require('metalsmith-react-templates');
metalsmith.use(templates());
To specify additional options:
metalsmith.use(templates({
baseFile: 'base.html'
isStatic: true,
directory: 'templates'
}));
Usage Notes
Specifying Templates
If an rtemplate
field is set in the yaml
front matter of your markdown files, metalsmith-react-templates
will use the specified template instead of Default.jsx
.
You can also set noConflict
to false
and the plugin will use the template
field instead of rtemplate
field in the yaml
front matter.
Webpack / Build Systems
If you import css or any other non-standard JavaScript code using require
,
you might want to make use of the requireIgnoreExt
to ignore those files.
Options
All parameters are optional.
Parameter | Default Value | Description |
---|
baseFile | null | Specifies a file which the contents of the react template will render into.
This is similar to the index.html file which you React.render() your components in.
In your base file, put {{content}} in the location where you want your data will render into.
You may also override this value by placing a baseFile key in your source file's front matter. |
baseFileDirectory | null | Sets the directory which your baseFile resides. By default, it assumes your base file is in the same directory as your templates. |
defaultTemplate | Default.jsx | The default template file to use if no template is specified.
Set to '' or null if you do not want metalsmith to not apply template transformation on files that do not have a 'template / rtemplate' key present. |
directory | templates | Sets the directory which your react templates resides. |
extension | null | Option to rename your files to a specified extension. |
html | true | (alias) Sets the extension parameter to .html if it's not already set. |
isStatic | true | Since this is a static site generator, by default, it will render the React Templates using renderToStaticMarkup() .
However, you may choose to make a static site generator with React functionalities (similar to first render from server) and subsequently pull page routes via JavaScript / React.
Setting this parameter to false will cause templates to be parsed using renderToString() . |
noConflict | true | By default, this plugin will read from the rtemplate key in your yaml front matter. However, if this is the only templating plugin, you may set noConflict to false to use the template key instead. |
pattern | **/* | Specifies a file filter pattern. |
preserve | false | Stores a copy of un-templated contents into rawContents meta which you can access in your React components. |
requireIgnoreExt | [ ] | A list of extensions to ignore.
For example, {requireIgnoreExt: ['.css']} would ignore declarations like require('file.css') |
templateTag | null | Accepts a function pattern(key) which returns a regex object used to find and replace template tags in your output file.
By default, template tags are assumed to be {{tag}} . You may use this to allow for other tag formats (eg. you may want <!--tag--> instead). Check the test case for an example. |
tooling | { } | Options to pass into the babel transpiler. |
Other Links
MIT © Gerald Yeo