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

@exsoinn/eslint-config-exsoinn

v1.0.1

Published

Common linting rules for Node.js apps

Downloads

2

Readme

eslint-config-exsoinn

banner

Enforcing Node.js code style since 2021.

Install

npm install --save-dev --save-exact @exsoinn/eslint-config-exsoinn@latest [email protected] eslint-config-standard@"<18" eslint-plugin-import@"<3" eslint-plugin-n@"<16" eslint-plugin-promise@"<7" eslint-config-serverless-stack@"<1" typescript-eslint@"<9" @stylistic/eslint-plugin-ts

Prepare Your Project

  1. Create a file called .eslintrc.yml and add the following contents to it:
extends:
  - '@exsoinn/eslint-config-exsoinn'
  1. In WebStorm enable ESLint. Go to Preferences | Languages & Frameworks | JavaScript | Code Quality Tools | ESLint and select the Automatic ESLint configuration radio button.

  2. Make WebStorm reformat code (⌥⌘L) according to ESLint rules by doing the following. Note that you need to repeat these steps if you update ESLint rules,

    1. Right-click on .eslintrc.yml, select Apply ESLint Code Style Rules.
    2. Go to Editor | Code Style | TypeScript, click Set From... and select JavaScript.
    3. Automatically fix lint errors on saving, go to Languages & Frameworks | JavaScript | Code Quality Tools | ESLint, check the Run eslint --fix on save box.

Usage

In addition to problems getting reported in the IDE in real-time fashion, you can run ESLint to report errors and optionally fix them automatically via the command line:

npx lint # report errors, but do not fix them

# or 

npx lint-fix # automatically fix errors

Overriding ESLint Configs

Most times this won't be necessary, and you can use as-is the ESLint rules that this configuration provides. But if you need to override any of the inherited ESLint configs, you can just add them to the .eslintrc.yml file. The details of how to configure ESLint are beyond the scope of this document, but you can go here to learn more.

Developer

If you need to update this package, run below commands to release a new version, making sure you strictly adhere to NPM semver rules:

  • npm run release:dry-run # a dry run gives you a chance to review the resulting new version
  • npm run release # performs a release, publishing the updated package to the NPM registry