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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@yaml-js/config-prettier

v0.1.4

Published

yaml-js shared prettier configuration

Downloads

4

Readme

YAML-JS Prettier Configuration

This repository provides a shared Prettier configuration to be used across all projects under the yaml-js umbrella. The goal is to maintain consistent code formatting and style throughout the entire ecosystem.

Table of Contents

Installation

To use the shared Prettier configuration in your project, follow these steps:

1. Install Prettier and the shared configuration

First, install Prettier and the @yaml-js/config-prettier package as development dependencies:

npm install --save-dev @yaml-js/config-prettier

or

yarn add -D @yaml-js/config-prettier

2. Create or update your .prettierrc file

Add the following to your .prettierrc file to extend the shared configuration:

"@yaml-js/config-prettier"

Alternatively, you can use a prettier.config.cjs file:

module.exports = {
  ...require("@yaml-js/config-prettier")
};

3. Add a format script to your package.json

To easily format your code, add a script in your package.json:

{
  "scripts": {
    "format": "prettier --write ."
  }
}

Usage

Once the configuration is set up, you can format your code by running the following command:

yarn run format

This will apply the shared Prettier rules across your project, ensuring consistency.

Configuration

The @yaml-js/config-prettier package includes a set of predefined rules aimed at enforcing a consistent coding style. While it is possible to override specific rules in your .prettierrc or prettier.config.cjs file, please note that doing so is generally not advisable, as it contradicts the primary purpose of this package.

For example, to change the print width:

module.exports = {
  ...require("@yaml-js/config-prettier"),
  "printWidth": 100
};

Refer to the Prettier documentation for a full list of available options.

Contributing

We welcome contributions to improve this configuration. If you have suggestions or find issues, please open an issue or a pull request.

Development

To make changes to the shared configuration, follow these steps:

  • Clone the repository.
  • Install dependencies with npm install.
  • Make your changes in the prettier.config file.
  • Test your changes by running the formatting command on test files.
  • Submit a pull request with a clear description of the changes.

License

This project is licensed under the MIT License. See the LICENSE file for details.