npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

prettier-plugin-yaml

v1.3.0

Published

Additional YAML formatting options for Prettier

Readme

Install

npm install --save-dev prettier-plugin-yaml
pnpm add --save-dev prettier-plugin-yaml

Usage

Reference prettier-plugin-yaml in your Prettier config:

{
    "plugins": [
        "prettier-plugin-yaml"
    ]
}

If you’re using any other YAML plugins, make sure prettier-plugin-yaml is listed last.

Options

In addition to Prettier’s built-in options that affect YAML formatting, prettier-plugin-yaml offers additional configuration options.

interface PluginOptions {
    /**
     * Enforce a single block style for multi-line string values. Does not apply
     * to flow collections.
     */
    yamlBlockStyle?: 'folded' | 'literal' | undefined;
    /**
     * Enforce a single collection style for maps and sequences.
     */
    yamlCollectionStyle?: 'block' | 'flow' | undefined;
    /**
     * Quote all scalar mapping keys. Leaves YAML merge keys and explicitly
     * tagged non-string keys unchanged. Removes unnecessary quotes when disabled.
     * @default false
     */
    yamlQuoteKeys?: boolean | undefined;
    /**
     * Quote keys that match a specific pattern. Non-string keys are matched
     * based on their string representation. Leaves YAML merge keys and explicitly
     * tagged non-string keys unchanged. Doesn’t affect keys that must be quoted
     * anyway.
     */
    yamlQuoteKeysMatching?: string | undefined;
    /**
     * Quote all string values. Takes precedence over `yamlBlockStyle`. Removes
     * unnecessary quotes when disabled.
     * @default false
     */
    yamlQuoteValues?: boolean | undefined;
    /**
     * Quote values that match a specific pattern. Non-string values are matched
     * based on their string representation. Leaves explicitly tagged non-string
     * values unchanged. Takes precedence over `yamlBlockStyle`. Doesn’t affect
     * values that must be quoted anyway.
     */
    yamlQuoteValuesMatching?: string | undefined;
}

FAQ

How do I automatically quote integer values?

Use yamlQuoteValuesMatching. Unlike yamlQuoteValues, which only applies to string values, it matches values based on their string representation. For example, to quote integers:

{
    "yamlQuoteValuesMatching": "^\\d+$"
}

You can quote boolean and null values similarly:

{
    "yamlQuoteValuesMatching": "^(true|false|null)$"
}

To quote mapping keys, use yamlQuoteKeys and yamlQuoteKeysMatching.

Why is the pattern a string instead of a regular expression?

yamlQuoteValuesMatching and yamlQuoteKeysMatching accept strings due to a limitation in how Prettier handles configuration values. RegExp is not a supported type, so the pattern must be provided as a string.

Internally, the plugin applies the pattern as new RegExp(pattern). Remember to escape backslashes and other special characters accordingly.

Related

License

MIT © Dom Porada