Quick Tip #011—Use local plugins to reduce config file size
Is your .eleventy.js file getting too large? You can create your own plugin to move some code out.
First, create a plugin file. We recommend creating a config or _config folder in your project to store config files in. Make sure that folder isn’t getting copied out to your built site. Then create a file in that folder. It doesn’t matter what you name it.
Filename config/local-plugin.js
module.exports = function (eleventyConfig) {
// Move any code you want from `.eleventy.js` to here
};WARNING:
Any variables defined in your
.eleventy.js file will not be available to your plugin. Consider moving those variables into your plugin file, or passing them in as options.Next, use the eleventyConfig.addPlugin() method to add your plugin.
Filename .eleventy.js
module.exports = function (eleventyConfig) {
eleventyConfig.addPlugin(require("./config/local-plugin.js"));
};All Quick Tips
#001—Inline Minified CSS#002—Inline Minified JavaScript#003—Add Edit on GitHub Links to All Pages#004—Zero Maintenance Tag Pages for your Blog#005—Super Simple CSS Concatenation#006—Adding a 404 Not Found Page to your Static Site#007—Fetch GitHub Stargazers Count (and More) at Build Time#008—Trigger a Netlify Build Every Day#009—Cache Data Requests#010—Transform Global Data using an `eleventyComputed.js` Global Data File#011—Use local plugins to reduce config file size#011—Draft Posts using Computed Data- View all of the Eleventy Quick Tips.