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

@kitschpatrol/prettier-config

v4.7.12

Published

Prettier configuration for @kitschpatrol/shared-config.

Downloads

227

Readme

@kitschpatrol/prettier-config

NPM Package @kitschpatrol/prettier-config License: MIT

Prettier configuration for @kitschpatrol/shared-config.

Overview

It's a shared Prettier config.

See @kitschpatrol/shared-config for the recommended single-package approach.

Setup

To use just this Prettier config in isolation:

  1. Install the .npmrc in your project root. This is required for correct PNPM behavior:

    pnpm dlx @kitschpatrol/repo-config --init
  2. Add the package:

    pnpm add -D @kitschpatrol/prettier-config
  3. Add the starter .prettierrc.js and .prettierignore files to your project root, and add any customizations you'd like:

    pnpm exec prettier-config --init

Usage

The Prettier binary should be picked up automatically by VS Code plugins.

You can call it directly, or use the script bundled with the config.

Integrate with your package.json scripts as you see fit, for example:

"scripts": {
  "lint": "prettier-config --check"
  "format": "prettier-config --fix"
}

You might need to pass certain plugins in explicitly. The shared-config --fix and shared-config --lint scripts take care of this for you.

CLI

Command: prettier-config

Prettier configuration for @kitschpatrol/shared-config.

Usage:

prettier-config [<file|glob> ...]

| Option | Argument | Description | | ------------------------ | -------- | ---------------------------------------------------------------- | | --check-c | | Check for and report issues. Same as prettier-config. | | --fix-f | | Fix all auto-fixable issues, and report the un-fixable. | | --init-i | | Initialize by copying starter config files to your project root. | | --print-config-p | <path> | Print the effective configuration at a certain path. | | --help-h | | Print this help info. | | --version-v | | Print the package version. |

Ruby support

Ruby formatting Expects a global Ruby install >=2.7 via rbenv at ~/.rbenv/shims/ruby with the following gems:

  • bundler
  • prettier_print
  • syntax_tree
  • syntax_tree-haml
  • syntax_tree-rbs

Note: Do not add plugins: ['prettier-plugin-ruby'] to the per-file scope, it must be global.

Tabs vs. spaces

Tabs are unambiguously preferred wherever the file format specification does not mandate spaces.

The reluctant exceptions are:

JSON

Despite widely accepted FUD regarding JSON requiring spaces, the specification indicates otherwise.

YAML

Spaces are required by the specification.

Markdown and MDX

Spaces are not technically required, but are specified in alignment with the Remark project's conclusions and to prevent fragility in YAML frontmatter. (TODO: Need 4 spaces instead of 2?)

License

MIT © Eric Mika