Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Breaking: Aliased template syntax must be explicitly listed in template formats #3302

@zachleat

Description

@zachleat

Using https://www.11ty.dev/docs/languages/custom/#aliasing-an-existing-template-language

eleventyConfig.addExtension("markdown", {
	key: "md",
});

Any files with the .markdown extension were previously included if md was included in your project template format keys. As we unlock the power to more complex aliases in 3.0, this is changing.

You will now need to explicitly add markdown in --formats=markdown or via eleventyConfig.addTemplateFormats("markdown") to process .markdown files in your project.

This was more important as more and things chain to the 11ty.js template type (11ty.tsx, 11ty.jsx, 11ty.ts, etc).

Metadata

Metadata

Assignees

No one assigned

    Labels

    breaking-changeThis will have to be included with a major version as it breaks backwards compatibility.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions