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

@lottiefiles/prettier-config

v3.0.0

Published

Shared Prettier config for LottieFiles projects

Downloads

227

Readme

@lottiefiles/prettier-config

Shared Prettier configuration.

Table of contents

Installation

1. Install plugin and dependencies.

Install Prettier and this plugin by running:

# Normal repository? Install in the project root.
pnpm add -D prettier @lottiefiles/prettier-config

# Monorepo? Install Prettier in the project root workspace.
pnpm add -DW prettier @lottiefiles/prettier-config

2. Create configuration file

Create a prettier.config.cjs file in your project root with the contents below:

module.exports = {
  ...require('@lottiefiles/prettier-config'),
};

Usage

Create a npm script entry in the root package.json as follows:

{
  "scripts": {
    "format": "prettier --loglevel=warn --no-editorconfig --write ."
  }
}

You can then run pnpm format to format your project using the command line or in CI pipelines.

You can use the editor integration options described below to get your files formatted as you save them in the IDE.

Customizing configuration

Do this only if absolutely required

You can override the company-wide base configuration by setting values in the prettier.config.cjs file.

module.exports = {
  ...require('@lottiefiles/prettier-config'),

  // Overrides:
  semi: false,
};

Integrations

IDE Integration

Read the Editor Integration documentation at the Prettier website for how to integrate with all IDEs.

VS Code

  1. Install the prettier-vscode extension from the marketplace.
  2. Add the following content to the settings.json file:
{
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.formatOnSave": true
}

Note: If you prefer to apply the configuration to a project only, add the settings content above to a file named settings.json file in the .vscode folder at the root of your project. Create the file if it does not exist.

Lint-Staged Integration

Integrate formatting code before code is commited using git pre-commit hook events via lint-staged. (See docs on how to setup lint-staged)

lint-staged.config.cjs

module.exports = {
  '*': 'prettier --plugin=prettier-plugin-package --ignore-unknown --loglevel=warn --no-editorconfig --write',
};

Changelog

See CHANGELOG.md for the latest changes.