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

@naverpay/eslint-config

v1.0.7

Published

eslint config for naverpay

Downloads

218

Readme

@naverpay/eslint-config

네이버페이 스타일 가이드에 맞게 lint rule을 커스텀하여 제공합니다.

설치 방법

npm install @naverpay/eslint-config -D

사용 방법

프로젝트 환경에 알맞는 config를 extend 합니다.

  • @naverpay/eslint-config/front
    • JS로 작성된 react17+ 환경에서 사용합니다.
  • @naverpay/eslint-config/node
    • JS로 작성된 node 환경에서 사용합니다.
  • @naverpay/eslint-config/typescript
    • TS로 작성된 react17+ 환경에서 사용합니다.
  • @naverpay/eslint-config/typescript/next
    • TS로 작성된 Next12+ 환경에서 사용합니다.
// .eslintrc
{
    "extends": ["@naverpay/eslint-config/typescript"]
}

CLI

package.json에 스크립트를 추가하여 lint 검사를 할 수 있습니다.

// package.json
{
    "scripts": {
        "lint": "eslint '**/*.{js,jsx,ts,tsx}'",
        "lint:fix": "eslint '**/*.{js,jsx,ts,tsx}' --fix",
    }
}

husky & lint-staged를 사용해서 commit 또는 push 전에 스타일 확인을 자동화할 것을 권장합니다.

Integrating with IDE

  • code-style에서는 Formatting을 위해 Prettier를, Code-quality를 위해 ESLint를 사용하고 있습니다. (Prettier vs. Linters)
  • Prettier는 여기를 참고해주세요.
  • IDE에서 AutoFix 하기 위해 아래 설정이 필요합니다.

VSCode

  1. ESLint Extension을 설치합니다.
  2. IDE에서 Command Palette(CMD/CTRL + Shift + P)를 열고 settings.json을 입력하여 설정파일을 오픈합니다.
  3. 아래 설정을 추가하면 파일 저장시 ESLint rule에 맞게 autofix 할 수 있습니다.
{
    "editor.codeActionsOnSave": {
        "source.fixAll.eslint": "explicit"
    },
}

WebStorm

Settings > Language > JavaScript > Code Quality > ESLint > Automatic ESLint configuration 을 설정합니다.