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

@logic-warlock/config

v1.1.0

Published

Configuration for applying elsint rules and git commits to a JavaScript project.

Downloads

4

Readme

Config

This package allows an easy setup for a dev environment.

Installation

You can install this package with npm.

npm install @logic-warlock/config

Or with Yarn.

yarn add @logic-warlock/config

Setup

Once installed you need to create or update several files.

Linting

This project comes with several @logic-warlock eslint configs.

Now you just need to extend these packages from within a .eslintrc file.

{
  "extends": ["@logic-warlock", "@logic-warlock/react", "@logic-warlock/typescript"]
}

If you are using @logic-warlock/eslint-config-typescript then you will also need to specify a parser.

{
  "parser": "@typescript-eslint/parser"
}

You will also need to specify a parserOptions parameter that has a nested project that points to a .tsconfig file. For example the .eslintrc file would look something like:

{
  "extends": ["@logic-warlock", "@logic-warlock/react", "@logic-warlock/typescript"],
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "project": './tsconfig'
  }
}

If you don't have a .tsconfig file you can run tsc --init to generate one. You must already have TypeScript installed.

Environment

Prettier

Just create a .prettierrc file and add:

{
  "arrowParens": "always",
  "bracketSpacing": true,
  "endOfLine": "lf",
  "jsxBracketSameLine": false,
  "jsxSingleQuote": false,
  "printWidth": 100,
  "quoteProps": "as-needed",
  "semi": false,
  "singleQuote": true,
  "tabWidth": 2,
  "trailingComma": "all",
  "useTabs": false
}

Git-Hooks

To get git Hooks working properly you'll need to create a few files within your root directory.

husky.json

Add the following to your husky.json file. This will run any commands you list within lint-staged, and the apply conventional commits to your staged commits. You can add any additional commands to the hooks file. The command for prepare-commit-msg is used in order for commitizen to run properly.

{
  "hooks": {
    "pre-commit": "lint-staged",
    "prepare-commit-msg": "exec < /dev/tty && git cz --hook || true"
  }
}

lintstaged.json

Add the following to your lintstaged.json file. This will run prettier, and lint your code before it gets committed. These commands will be run within .js, .jsx, .ts, and .tsx files. You can edit or add any commands within this file.

{
  "*.{js,jsx,ts,tsx}": [
    "prettier --write --ignore-path .gitignore",
    "git add",
    "eslint . --ignore-path .gitignore"
  ]
}

commitizen

Add the following to your commitizen.json file. This path just specifies, well, the path to initiate commitizen.

{
 "path": "cz-conventional-changelog"
}