Stable: 3.1.2
Canary: 4.0.0-alpha.6

Data Deep Merge

On this page

Using the override prefix

Feature Removed

This feature was removed in Eleventy v4.0. Read more at GitHub Issue #3937 (originally inspired by GitHub Issue #147).

Feel free to head over to the previous Eleventy version of the docs for this documentation. Historically, it may be important to remember that the default for this feature was changed to true in Eleventy v1.

eleventy.config.js

ESM CommonJS

export default function (eleventyConfig) {
	// throws an error in Eleventy v4
	eleventyConfig.setDataDeepMerge(false);

	// is a no-op in Eleventy v4
	eleventyConfig.setDataDeepMerge(true);
};

module.exports = function (eleventyConfig) {
	// throws an error in Eleventy v4
	eleventyConfig.setDataDeepMerge(false);

	// is a no-op in Eleventy v4
	eleventyConfig.setDataDeepMerge(true);
};

Using the `override:` prefix

The override: prefix in the Data Cascade is still available! Read more about override: on the Data Cascade documentation.

Data Deep Merge

Using the override: prefix

Other pages in Data Cascade

Using the `override:` prefix