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

@clearpeaks/code-linting-style

v2.1.19

Published

A TSLint and Prettier config for ClearPeaks

Downloads

199

Readme

Linters for standardize the code

This repo contains the different configuration files and dependencies for different linters.

Those files will be extended by the proper files of the projects, as is explained below.

Install

If you are using yarn

yarn add --dev @clearpeaks/code-linting-style

If you are using npm

npm install @clearpeaks/code-linting-style --save-dev

Git Hook

In package.json, at scripts level, add the following hook to run prettier and linter before each commit

{
  "scripts": {
    ...
  },
  "husky": {
    "hooks": {
      "pre-commit": "pretty-quick --staged && tslint -c ./tslint.json 'src/**/*.ts'"
    }
  }
}

Deprecarion warning. Upgrading from 0.14

With the version 0 the precommit hook was being declared inside of the scripts. Please change that logic on your projects.

{
  "scripts": {
    "precommit": "pretty-quick --staged && tslint -c ./tslint.json 'src/**/*.ts'"   // Before (BAD)
  },
  "husky": {
    "hooks": {
      "pre-commit": "pretty-quick --staged && tslint -c ./tslint.json 'src/**/*.ts'"    // Now (GOOD)
    }
  }
}

Note: Version 1 of husky require node version >=6, while Husky 2 require node>=8, so we are keeping husky 1 for compatibility.

Tslint

Create tslint config file

touch tslint.json

Add the following content to that file to extend from the clearpeaks package

{
  "defaultSeverity": "error",
  "extends": ["@clearpeaks/code-linting-style/tslint.js"],
  "jsRules": {
    "no-empty": true
  }
}

You can find more info about tslint rules here

Prettier

Create a prettier config file

touch .prettierrc.js

Add the following content to that file to extend from the clearpeaks package

const clearpeaksConfig = require('@clearpeaks/code-linting-style/prettier-conf');
module.exports = clearpeaksConfig;

You can find more info about prettier option/config rules here

More info about prettier configuration file here

ESLint

Create eslint config file

touch .eslintrc.js

Add the following content to that file to extend from the clearpeaks package

module.exports = {
  extends: [
    "./node_modules/@clearpeaks/code-linting-style/.eslintrc.js",
    "prettier"
    ]
}

Note: I had to use the following hook to make the precommit work

  "husky": {
    "hooks": {
      "pre-commit": "./node_modules/.bin/pretty-quick --staged && ./node_modules/.bin/eslint --ext .js lib/ --fix"
    }
  },

Installing some extra packages npm i -D eslint eslint-config-prettier husky prettier pretty-quick You can find more info about eslint rules here

Tips

If you are using prettier in vscode, you can enable autoprettify on save, to prettify you files after saving them Add the following config to the User Settings.

To avoid unwanted behaviour with prettier and html, we recommend you to disable runing prettier on save for html files

"editor.formatOnSave": true,
"prettier.eslintIntegration": true,
"[html]": {
  "editor.formatOnSave": false
},

Deploy a new version of the package

Once the PR has been approved:

  1. Increase the semver npm version <patch|minor|major> // This creates a new commit
  2. Publish the package npm publish
  3. Push autogenerated commit git push
  • Note, maybe you will need to login the first time: npm login and use the credentials of ClearPeaks

BREAKING CHANGES 2.x -> 3.x

Upgrading to 3.x version, requires to have Node.js 10+