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

lint-fix-nodemon

v1.1.0

Published

watch files and run eslint+fix+nodemon without double restarts

Downloads

37

Readme

lint-fix-nodemon

Watch your files and run ESLint + fix + nodemon on save

WHY DO YOU NEED THIS?

  1. Avoid a double restart when eslint fixes your files (nodemon would normally detect the initial change and then the fix change)
  2. Don't get stuck if linting or starting the server fails - we just keep watching and trying again on each save

Installation

npm install lint-fix-nodemon --save-dev or yarn add lint-fix-nodemon -D

Setup

You can run it with npx lint-fix-nodemon or normally you should just add a script to your package.json file.

I usually name it "dev" ("dev": "lint-fix-nodemon") so you can run npm run dev

Configuration

By default, it will assume nodemon should run the script specified as your "main" in your package.json file. Otherwise you can also pass it in as an argument -- for example: lint-fix-nodemon ./api/start.js

Other configuration in terms of what files to watch and lint will be read from the nodemonConfig entry in your package.json file

It will automatically ignore your node_modules folder and any files/folders that start with "."

Setting ESLint extensions

Normally when running eslint from the cli, you must specify the extensions you wish to run on, or it will automatically just default to .js files only.

To avoid having to set it again, we copy the extension settings from the nodemon config set in package.json file. This may mean you need to add some ignore rules in your eslintrc file, to ignore certain file types that you don't want to lint, but you do want changes to cause a nodemon restart.

An example package.json file

{
  ...
  "scripts": {
    "dev": "lint-fix-nodemon api/start.js",
    ...
  },
  "nodemonConfig": {
    "watch": ["api/"],
    "ignore": ["api/scripts"],
    "ext": "js,json,ts"
  },
  ...
}