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

@veriff/prettier-config

v2.1.2

Published

Shared prettier configuration.

Downloads

678

Readme

prettier-config

This package contains Prettier configuration that enforce code formatting conventions.

Usage

At first, install prettier and the package:

npm i prettier @veriff/prettier-config --save-dev

To apply the configuration you need to add prettier to your project's dependencies and create a .prettierrc.json file in the root with the following contents:

"@veriff/prettier-config"

If you like to overrride any prettier options, create .prettierrc.js (docs):

module.exports = {
    ...require("@veriff/prettier-config"),
    //
    // any prettier option overrides -  https://prettier.io/docs/en/options.html
    //
    'printWidth': 150,
};

With ESLint

Setting up just eslint with @veriff/eslint-config is recommended and usually enough. However, you still might prefer to let prettier take care of formatting. In this case you need to adjust eslint configuration to avoid any possible conflicts with prettier.

Ar first, install eslint-config-prettier to disable conflicting eslint rules:

npm i eslint-config-prettier --save-dev

Then extend your eslint configuration with it:

{
  "extends": [
    "@veriff/eslint-config/<config-you-use>",
    "prettier"
  ]
}

This will disable all eslint rules that might conflict with prettier. It means that code formatting is now on prettier and you should make sure it works on every commit and checks formatting on the CI.

More details on this approach you can find in the official prettier documentation.

With Stylelint

Setting up just stylelint with @veriff/stylelint-config is recommended and usually enough. However, you still might prefer to let prettier take care of formatting. In this case you need to adjust stylelint configuration to avoid any possible conflicts with prettier.

Ar first, install stylelint-config-prettier to disable conflicting stylelint rules:

npm i stylelint-config-prettier --save-dev

Then extend your stylelint configuration with it:

{
  "extends": [
    "@veriff/stylelint-config",
    "stylelint-config-prettier"
  ]
}

This will disable all stylelint rules that might conflict with prettier. It means that code formatting is now on prettier and you should make sure it works on every commit and checks formatting on the CI.

More details on this approach you can find in the official prettier documentation.