nodejs / nodejs/citgm

Add Chokidar to the mix?

Open
#446 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

additional-modules
Dominant language
JavaScript
Stars
606
Forks
157
Avg merge
3d 23h
Merged PRs (30d)
3

Description

Apparently, an update or something in v8.0.0 is causing issues with Chokidar, so it might be a good idea to add that to the cigtm list.

As for who uses it:

  • The CLIs for PostCSS, Babel, ESLint, among others, directly use it for their file watching.
  • Gulp's gulp.watch directly uses it
  • Browserify's watchify directly uses it
  • Among about 2k others (directly)

It also sees about 8-9M downloads monthly.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the CITGM list and reviewing how existing npm modules are registered. Add Chokidar following the established entry format, then run the relevant CITGM checks to verify that it is included in the canary testing set.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
testing-qa
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.