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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@kkulebaev/prettier-config

v0.2.0

Published

A Prettier shareable config for projects using Prettier

Downloads

449

Readme

@kkulebaev/prettier-config

A Prettier shareable config for projects using Prettier

Installation

npm install -D @kkulebaev/prettier-config

# or with yarn
yarn add -D @kkulebaev/prettier-config

# or with pnpm
pnpm add -D @kkulebaev/prettier-config

This is only a shareable configuration. It does not install Prettier or any other part of the tool chain.

Usage

Reference it in package.json using the prettier property:

{
  "name": "my-projects-name",
  "prettier": "@kkulebaev/prettier-config",
  "devDependencies" : {
    "@kkulebaev/prettier-config": "^0.1.0"
  }
}

If you don't want to use package.json, you can use any of the supported extensions to export a string:

// `.prettierrc.json`
"@kkulebaev/prettier-config"
// `prettier.config.js` or `.prettierrc.js`
module.exports = '@kkulebaev/prettier-config'

Extending Shared Configurations

This configuration is not intended to be changed, but if you have a setup where modification is required, it is possible. Prettier does not offer an "extends" mechanism as you might be familiar from tools such as ESLint.

To extend a configuration you will need to:

  1. Import/Require this sharable config from within your own configuration. This means you must be using a JavaScript version of a Prettier configuration file.
  2. Extend your modification on top of the shared config using something like Object destructuring, Object.assign(), or lodash.merge()
  3. Export the modified configuration

Prettier uses cosmiconfig for configuration file support. This means you can configure prettier via:

  • A .prettierrc file, written in YAML or JSON, with optional extensions: .yaml/.yml/.json.
  • A .prettierrc.toml file, written in TOML (the .toml extension is required).
  • A prettier.config.js or .prettierrc.js file that exports an object.
  • A "prettier" key in your package.json file.

...

Sharing configurations

Note: This method does not offer a way to extend the configuration to overwrite some properties from the shared configuration. If you need to do that, import the file in a .prettierrc.js file and export the modifications, e.g:

module.exports = {
  ...require("@kkulebaev/prettier-config"),
  semi: false
};

Source

For example, if you need to change it so that semicolons are required:

// `prettier.config.js` or `.prettierrc.js`
const prettierConfigStandard = require('@kkulebaev/prettier-config')
const merge = require('lodash.merge')

const modifiedConfig = merge(
  {},
  prettierConfigStandard,
  {
    semi: true,
    // ... other modified settings here
  }
)

module.exports = modifiedConfig