netlify-cms-loader v0.7.3

netlify-cms-loader

A webpack loader to require() content from the Netlify CMS by referencing collections via their configured name.

The loader processes the files of a collection and outputs their content as an array of objects. Additionally all processed CMS entries will be converted to JSON and added to the final Webpack result.

By default everything but the body field is included in the output in order to not bloat the Webpack bundle with content, that may not be needed right away.

Note: This is a 3rd-party loader. I am in no way affiliated with Netlify, though I wholeheartedly recommend anyone to check them out.

Breaking changes will occur with every minor version until 1.0.0

For now I recommend to use this loader only in an experimental way and not in any real production environment

Loader options (and defaults)

What the loader does

• loads and processes the required collection files
• adds hasBody property to the output, if file has a body field
• adds filePath property to the output, if a .json file is emitted
• returns collection data as array of objects
• emits processed collection files as JSON to outputDirectory

Setup

Install the loader as a dev dependency

npm install netlify-cms-loader --save-dev

The loader will only emit its own .json files of processed CMS entries.

It does not copy any static assets, such as the files in the media_folder of the CMS. Make sure that those files get copied to the public_folder path specified in your config.yml.

You can use the copy-webpack-plugin for this.

/* config.yml
media_folder: "src/uploads"
public_folder: "uploads"
*/
new CopyWebpackPlugin([
	{ from: 'src/admin', to: 'admin' },
	{ from: 'src/uploads', to: 'uploads' }
])

Using the loader

The loader should be used inline.

const allMyPosts = require("netlify-cms-loader?collection=posts!admin/config.yml")

While that first example looks a bit unwieldy, with only some configuration it can be made much more concise and easy to read.

const allMyPosts = require("cms?posts!")

I think the webpack inline loader syntax of question and exclamation marks even makes some good sense here in a coincidental way... from the cms? get posts!

To achieve this I would recommend two things. First create an environment variable called NETLIFY_CMS_LOADER_CONFIG and assign it the path to the config.yml file. How the variable should be declared is up to you. This is only one example.

//package.json
"scripts": {
	// ...
	"dev": "NODE_ENV=development NETLIFY_CMS_LOADER_CONFIG=src/admin/config.yml webpack-dev-server --config build_config/webpack.config.js"
},

This will let you omit the config.yml file from the inline loader.

Second is to create a loader alias to shorten netlify-cms-loader to just cms

//in your webpack config
resolveLoader: {
	modules: [path.resolve('node_modules')],
	alias: {
		"cms": "netlify-cms-loader"
	}
}

All done.

You can use the loader either with a query string or an options object. There is also a shorthand version where you specify the name of a collection as the only argument.

Single files of a file collection can also be imported via shorthand by separating the collection and name of the file entry with a "/" require("cms?someCollection/someName!")

By default the body field of a CMS entry is not included in the loaders output. The presence of a body will be indicated by the hasBody property being present in output object.

The client can then fetch an entries .json file when its body data is needed. Alternatively set includeBody: true to always include body content in the loaders output.

Examples:

Using a query string to fetch the 2 newest items in a collection

const latestPosts = require("cms?collection=posts&limit=2!")

// Example output:
[{
	title: "The newest post",
	author: "John Doe",
	image : "/uploads/neatImage.jpg",
	hasBody: true,
	filePath : "cms/posts/2018-08-02_the-newest-post.json",
},{
	title: "A slightly older post",
	author: "John Doe",
	image : "/uploads/greatPicture.jpg",
	hasBody: true,
	filePath : "cms/posts/2018-07-24_slightly-older-post.json",
}]

Using a template string (notice the backticks ` ... ` ) with an option object to fetch all items of the 'news' collection, but only return the title and date fields.

const allNews = require(`cms?{
	collection: 'news',
	fields: ['title','date']
}!`)

// Example output:
[{
	title: "Some Title",
	date : "2017-08-02T02:55:59.161Z",
	hasBody: true,
	filePath: "cms/news/2017-08-02_someNews.json"
},{/*...*/},{/*...*/},{/*...*/},{/*...*/}]

Fetch all news items by using a shorthand for the collection name. (if only a single query parameter is included, then that will used as argument for the collection name)

const allNews = require("cms?news!")

// Example output:
[{
	title: "Some Title",
	author: "John Doe",
	tags: ["Festival","Outdoors"],
	date : "2017-08-02T02:55:59.161Z",
	hasBody: true,
	filePath: "cms/news/2017-08-02_someNews.json"
},{/*...*/},{/*...*/},{/*...*/},{/*...*/}]

Using shorthand to fetch a single file of a file collection. (This will return an object directly instead of an array of objects)

const john = require("cms?people/JohnDoe!")

// Example output:
{
	firstName: "John",
	lastName: "Doe",
	age: 29,
	location: "Earth",
	filePath: "cms/people/JohnDoe.json"
}

See a live example of a test-site using the loader to require some content here.

Code example of a Vue component using the loader here.

Caveats

• Currently the loader only processes files that contain front-matter and can be directly parsed by the gray-matter library or are plain .json files.
• The same collection should not be required in multiple places while using different options. Doing so will result in the loader outputting 2 separate arrays, which may have overlapping entries, thus unnecessarily increasing the bundle size.