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

@powerhome/eslint-config

v0.2.2

Published

Provides eslint-config and Prettier formatting for Power Home Remodeling apps.

Downloads

556

Readme

@powerhome/eslint-config

Provides eslint-config and Prettier formatting for Power Home Remodeling apps.

Installation

Add this line to your application's package.json:

  "devDependencies": {
    ...
    "@powerhome/eslint-config": "0.1.0",
    ...
  }

And then yarn:

$ yarn

Usage

Assuming it's a typescript app, add an extends line to your .eslintrc.json:

{
  ...
  extends: [
    ...
    "@powerhome",
  ],
  ...
}

Flow type apps

For flow-based apps, replace @powerhome by @powerhome/eslint-config/flow. Note that usage of Flow at Power is not recommended, and all projects should migrate to TypeScript; this set of rules is provided only for transitionary purposes and will be removed in future releases.

Prettier

Prettier takes code formatting decisions while ESlint cares about code quality measurements. Both tools were put together into the same package since they both handle code quality in JS.

To install Prettier rules into your application simply add the following line to your package.json and Power's standards for code formatting will be loaded when you run Prettier.

"prettier": "@powerhome/eslint-config/prettier"

Prettier and ESlint rules might conflict sometimes. To find out rules that are conflicting you can run the following command line in your project:

yarn eslint-config-prettier path/to/main.js

That's a helper method created by the eslint-config-prettier package that points out which rules are conflicting.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/powerhome/power_linting.

License

The package is available as open source under the terms of the MIT License.