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

@zzjiaxiang/eslint-config

v1.0.16

Published

zzjiaxiang's ESLint config

Downloads

7

Readme

@zzjiaxiang/eslint-config

  • Only support vue3.
  • Support JavaScript and TypeScript also markdown.
  • ESLint analyzes code to find problems.
  • Prettier auto fix for formatting.

Preset use eslint-plugin-prettier runs Prettier as an ESLint rule. and use eslint-config-prettier to disable all formatting-related ESLint rules.

Install

npm install -D eslint @zzjiaxiang/eslint-config
or
pnpm add -D eslint @zzjiaxiang/eslint-config

Config .eslintrc

{
  "root": true,
  "extends": "@zzjiaxiang"
}

The preset has exclude some files that do not need to be checked,you also add file in .eslintignore.

Config .prettierrc

The preset uses the default prettier rules. you can override the rules in your .prettierrc file.

{
  // such as
  "semi": false,
  "singleQuote": true
}

Setting .prettierignore exclude files that do not formatting.

Setting you VS Code for auto fix

  • Your VS Code needs to install Prettier and Eslint extension also keep open prettier.
  • Add the following settings to your settings.json:
  "editor.formatOnSave": true,
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true,
    "source.organizeImports": false
  },
  "eslint.codeAction.showDocumentation": {
    "enable": true
  },
  // you can optional this following in your settings.json
  "eslint.validate": [
    "javascript",
    "typescript",
    "vue",
    "html",
    "markdown",
    "json"
  ],
  // Comment out the configuration related to Vue file formatting
  // "[vue]": {
  //   "editor.defaultFormatter": "Vue.volar"
  // },

TypeScript Rules

  • Setting some rules in the tsconfig.json in the project root.
  • preset extends @typescript-eslint/stylistic-type-checked, so setting compilerOptions.strictNullChecks help you check for possible null or undefined values, of course you can also close the rules "@typescript-eslint/prefer-nullish-coalescing": "off".
 // tsconfig.json
{

  "compilerOptions": {
    "strictNullChecks": true
  }

  // other config...
  // The following is optional.
  // add your rules here.
    "baseUrl": ".",
    "target": "es6",
    "module": "es2022",
    "moduleResolution": "Bundler",
    "esModuleInterop": true
}

override rules

you can override or close the rules.

// .eslintrc
{
  "root": true,
  "extends": "@zzjiaxiang",
  rules:{
    // your rules...
  }
}