Introduction
What?
This Prettier plugin (namely prettier-plugin-embed
) provides a configurable solution for formatting embedded languages in the form of template literals within JavaScript or TypeScript files.
Why?
Although Prettier has introduced the embedded-language-formatting
option for formatting embedded languages, it only supports two modes: auto
and off
. Therefore it doesn't allow for individual formatting adjustments for specific languages, nor does it support customizing the languages that require formatting and identifiers for identification. These limitations restrict the usability of this feature. For more detailed discussions, refer to: https://github.com/prettier/prettier/issues/4424 and https://github.com/prettier/prettier/issues/5588.
How?
By leveraging Prettier's plugin system, this plugin overrides the default embed
function of the estree
printer, so varieties of new languages can be hooked in through this function. Check this file to get an idea of how this is accomplished.
Features
-
Support for Additional Languages: Extend the embedded language formatting capability to include languages such as XML, SQL, PHP, and more.
-
Dual Identification Modes: Identify embedded languages by tags identifier`...`
or comments /* identifier */ `...`
preceding the template literals.
-
Customizable Language Identifiers: Customize the identifiers used for identifying the embedded languages.
-
Formatting Opt-out Mechanism: Offer the capability to deactivate formatting for certain identifiers, including the default ones (html
, css
...) supported by the embedded-language-formatting
option.
-
Configurable Formatting Style: Provide additional options to tailor the formatting style for embedded languages.
-
Strongly Typed API: Benefit from comprehensive type support for configuring this plugin's options when employing the Prettier API in TypeScript.
-
Easy Integration: Integrate with the existing Prettier setup seamlessly, requiring minimal configuration to get started.
Installation
npm i -D prettier-plugin-embed
Usage
Getting Started
This is a Prettier plugin, which follows the standard usage pattern of many other Prettier plugins:
Via --plugin
:
prettier --write main.ts --plugin=prettier-plugin-embed
Via the plugins
options:
await prettier.format(code, {
filepath: "main.ts",
plugins: ["prettier-plugin-embed"],
});
{
"plugins": ["prettier-plugin-embed"]
}
Quick Start Config Examples
Here're some quick start config examples to use this plugin for various embedded languages. Check beblow for a detailed explanation of all the available options.
An Overview of the Philosophy
To use this plugin, embedded-language-formatting
option must be set to auto
(which is the default setting as of now), because this option serves as the main switch for activating embedded language formatting.
This plugin does not aim to implement parsers or printers to support every newly added embedded language. Instead, ideally, it makes use of existing Prettier plugins for those languages and only adds formatting support when they are embedded in template literals.
Therefore, to enable formatting for a specific embedded language, the corresponding Prettier plugin for that language must also be loaded. For example, if you wish to format embedded XML language, you will need to load both this plugin and @prettier/plugin-xml
. To find out which other plugins are required when using this plugin, please refer to the Language-Specific Options section below.
Embedded languages to be formatted are required to be enclosed in the template literals, and are identified by the preceding tags identifier`...`
or block comments /* identifier */ `...`
. This plugin comes pre-configured with a built-in set of identifiers for identifying various embedded languages. For instance, using identifiers like xml
or svg
will trigger automatic formatting for the embedded XML language. You can specify an alternative list of identifiers using the embeddedXmlIdentifiers
option. The naming convention for these options follows the pattern of embedded<Language>Identifiers
for other languages as well. Further details on these options and how to configure them are also available in the Language-Specific Options section.
To exclude certain identifiers from being identified, including the default ones supported by the embedded-language-formatting
option, add them to the list of the embeddedNoopIdentifiers
option. Any matching identifiers listed in this option will take precedence over other embedded<Language>Identifiers
options, effectively disabling their formatting.
[!IMPORTANT]
Until this notice is removed, always specify identifiers explicitly and do not rely on the built-in defaults, as they may be subject to change.
Language-Specific Options
Supported embedded languages are:
Click Here to Toggle
NOOP
Option | Type | Default | Description |
---|
embeddedNoopIdentifiers | string[] | [] | Tag or comment identifiers that prevent their subsequent template literals from being identified as embedded languages and thus from being formatted. |
This option doesn't require other plugins and can override the native embedded language formatting. It serves as a way to turn off embedded language formatting for the specified language identifiers.
CSS
Option | Type | Default | Description |
---|
embeddedCssIdentifiers | string[] | ["css"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded CSS language. |
embeddedCssParser | "css" | "less"| "scss" | "scss" | The parser used to parse the embedded CSS language. |
Formatting embedded CSS language doesn't require other plugins and uses the parsers and printers provided by Prettier natively.
This can override the native formatting bahavior for embedded CSS language. If you want to keep the native behavior, set embeddedCssIdentifiers
to []
or other identifiers.
If you want to specify different parsers for different identifiers, check embeddedOverrides
.
ES (ECMAScript/JavaScript)
Formatting embedded ECMAScript language doesn't require other plugins and uses the parsers and printers provided by Prettier natively.
If you want to specify different parsers for different identifiers, check embeddedOverrides
.
GLSL
Option | Type | Default | Description |
---|
embeddedGlslIdentifiers | string[] | ["glsl", "shader"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded GLSL language. This option requires the prettier-plugin-glsl plugin. |
Formatting embedded GLSL language requires the prettier-plugin-glsl
plugin to be loaded as well.
GraphQL
Option | Type | Default | Description |
---|
embeddedGraphqlIdentifiers | string[] | ["graphql", "gql"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded GraphQL language. |
Formatting embedded GraphQL language doesn't require other plugins and uses the parsers and printers provided by Prettier natively.
This can override the native formatting behavior for embedded GraphQL language. If you want to keep the native behavior, set embeddedGraphqlIdentifiers
to []
or other identifiers.
HTML
Option | Type | Default | Description |
---|
embeddedHtmlIdentifiers | string[] | ["html", "xhtml"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded HTML language. |
embeddedHtmlParser | "html" | "vue" | "angular" | "lwc" | "html" | The parser used to parse the embedded HTML language. |
Formatting embedded HTML language doesn't require other plugins and uses the parsers and printers provided by Prettier natively.
This can override the native formatting behavior for embedded HTML language. If you want to keep the native behavior, set embeddedHtmlIdentifiers
to []
or other identifiers.
If you want to specify different parsers for different identifiers, check embeddedOverrides
.
INI
Option | Type | Default | Description |
---|
embeddedIniIdentifiers | string[] | ["ini", "cfg", "pro"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded INI language. This option requires the prettier-plugin-ini plugin. |
Formatting embedded INI language requires the prettier-plugin-ini
plugin to be loaded as well. And options supported by prettier-plugin-ini
can therefore be used to further control the formatting behavior.
JSON
Formatting embedded JSON language doesn't require other plugins and uses the parsers and printers provided by Prettier natively.
If you want to specify different parsers for different identifiers, check embeddedOverrides
.
LaTeX
Formatting embedded LaTeX language requires the prettier-plugin-latex
plugin to be loaded as well.
Markdown
Option | Type | Default | Description |
---|
embeddedMarkdownIdentifiers | string[] | ["md", "markdown"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded Markdown language. |
embeddedMarkdownParser | "markdown" | "mdx"| "remark" | "markdown" | The parser used to parse the embedded Markdown language. |
Formatting embedded Markdown language doesn't require other plugins and uses the parsers and printers provided by Prettier natively.
This can override the native formatting for embedded Markdown language. If you want to keep the native behavior, set embeddedMarkdownIdentifiers
to []
or other identifiers.
If you want to specify different parsers for different identifiers, check embeddedOverrides
.
The remark
parser is an alias of the markdown
parser.
PHP
Option | Type | Default | Description |
---|
embeddedPhpIdentifiers | string[] | ["php", "php5"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded PHP language. This option requires the @prettier/plugin-php plugin. |
Formatting embedded PHP language requires the @prettier/plugin-php
plugin to be loaded as well. And options supported by @prettier/plugin-php
can therefore be used to further control the formatting behavior.
Properties
Option | Type | Default | Description |
---|
embeddedPropertiesIdentifiers | string[] | ["properties"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded Properties language. This option requires the prettier-plugin-properties plugin. |
Formatting embedded Properties language requires the prettier-plugin-properties
plugin to be loaded as well. And options supported by prettier-plugin-properties
can therefore be used to further control the formatting behavior.
Ruby
Option | Type | Default | Description |
---|
embeddedRubyIdentifiers | string[] | ["ruby"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded Ruby language. This option requires the @prettier/plugin-ruby plugin. |
embeddedRubyParser | "ruby" | "rbs" | "haml" | "ruby" | The parser used to parse the embedded Ruby language. This option requires the @prettier/plugin-ruby plugin. |
Formatting embedded Ruby language requires the @prettier/plugin-ruby
to be loaded and its dependencies to be installed as well. And options supported by @prettier/plugin-ruby
can therefore be used to further control the formatting behavior.
If you want to specify different parsers for different identifiers, check embeddedOverrides
.
Sh (Shell)
Option | Type | Default | Description |
---|
embeddedShIdentifiers | string[] | ["sh"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded Shell language. This option requires the prettier-plugin-sh plugin. |
Formatting embedded Shell language requires the prettier-plugin-sh
plugin to be loaded as well. And options supported by prettier-plugin-sh
can therefore be used to further control the formatting behavior.
Note that prettier-plugin-sh
supports different variants of shell syntaxes and they are specified by the variant
option. If you want to specify different variants for different identifiers, check embeddedOverrides
.
SQL
Formatting embedded SQL language requires the prettier-plugin-sql
plugin or the prettier-plugin-sql-cst
plugin to be loaded as well. And options supported by prettier-plugin-sql
, or options supported by prettier-plugin-sql-cst
can therefore be used to further control the formatting behavior.
Note that prettier-plugin-sql
supports many different SQL dialects which are specified by the language
, database
or dialect
option. And prettier-plugin-sql-cst
also supports various parsers as shown above. If you want to specify different dialects or parsers for different identifiers, check embeddedOverrides
.
TOML
Option | Type | Default | Description |
---|
embeddedTomlIdentifiers | string[] | ["toml"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded TOML language. This option requires the prettier-plugin-toml plugin. |
Formatting embedded TOML language requires the prettier-plugin-toml
plugin to be loaded as well. And options supported by prettier-plugin-toml
can therefore be used to further control the formatting behavior.
TS (TypeScript)
Formatting embedded TypeScript language doesn't require other plugins and uses the parsers and printers provided by Prettier natively.
If you want to specify different parsers for different identifiers, check embeddedOverrides
.
XML
Option | Type | Default | Description |
---|
embeddedXmlIdentifiers | string[] | ["xml", "opml", "rss", "svg"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded XML language. This option requires the @prettier/plugin-xml plugin. |
Formatting embedded XML language requires the @prettier/plugin-xml
plugin to be loaded as well. And options supported by @prettier/plugin-xml
can therefore be used to further control the formatting behavior.
YAML
Option | Type | Default | Description |
---|
embeddedYamlIdentifiers | string[] | ["yaml", "yml"] | Tag or comment identifiers that make their subsequent template literals be identified as embedded YAML language. |
Formatting embedded YAML language doesn't require other plugins and uses the parsers and printers provided by Prettier natively.
Language-Agnostic Options
Option | Type | Default | Description |
---|
noEmbeddedIdentificationByComment | string[] | [] | Turns off /* identifier */ `...` comment-based embedded language identification for the specified identifiers. |
noEmbeddedIdentificationByTag | string[] | [] | Turns off identifier`...` tag-based embedded language identification for the specified identifiers. |
preserveEmbeddedExteriorWhitespaces | string[] | [] | Preserves leading and trailing whitespaces in the formatting results for the specified identifiers. |
noEmbeddedMultiLineIndentation | string[] | [] | Turns off auto indentation in the formatting results when they are formatted to span multi lines for the specified identifiers. |
embeddedOverrides | string | undefined | Option overrides for the specified identifiers. It should either be a stringified JSON or an absolute filepath to the option overrides file. See below for a detailed explanation. |
embeddedOverrides
This option is provided for users to override certain options based on identifiers. Due to the lack of support for using objects in prettier plugin options (https://github.com/prettier/prettier/issues/14671), it accepts a stringified json string, or a file path with an extension of .json
or .js
or .cjs
or .mjs
as its value. If no extension is provided, it will be treated as a .json
file. For relative paths, it will automatically figure out the prettier config location and use that as the base path.
The resolved value should be an array of objects. Each object in the array must have 2 fields: identifiers
and options
. The options
are considerred overrides that will be applied to the global options
of prettier for those idenfitiers
only. It's like the overrides
of prettier
, but it is identifier-based instead of file-based.
In a json file, the root is the array of objects. In a JavaScript file, the array of objects should be a default export, or a named export with the name embeddedOverrides
.
An example .json
file is:
[
{
"identifiers": ["sql"],
"options": {
"keywordCase": "lower"
}
},
{
"identifiers": ["mysql"],
"options": {
"keywordCase": "upper"
}
}
]
[!CAUTION]
Please note that not every option is supported to override. That largely depends on at which phase those options will kick in and take effect. For example, you can't override tabWidth
in embeddedOverrides
because this option is used in the printDocToString
phase, where prettier-plugin-embed
cannot override this option for only a set of specified identifiers. To find the list of unsupported options, please check the interface definition of EmbeddedOverride
in the source code.
Contributing
Bug fixes, new language support and tests are welcome. Please have a look at the project structure before getting started. Feel free to leave questions or suggestions.
License
MIT