← All tasks
javascriptlint-staged/lint-staged #1598Not a task: not reproduced

Run on all tracked files

envgap__lint-staged__lint-staged-1598

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.
Not a benchmark task.
  • In a clean container the reported failure did not reproduce, or the known fix did not make the project run.

02 / ENVIRONMENT RECIPE

Base commit
0a090981ef52a11fa4e4d90b6247f2310b5abc4f
Manifest
package.json
Reproduce
Awaiting issue-specific recipe
Run under trace
Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

lint-staged/lint-staged #1598 · read the original issue
I've seen https://github.com/lint-staged/lint-staged/issues/1519, but I didn't want to revive an 8 year old issue.

Keeping it short:

I have a repo with many packages across 7+ languages, each language with their own toolchains for tests, lints, formatting. I'd prefer
  * not to manage 7*3*(stage+CI) different CLI incantations and instead have guaranteed consistency
  * I'd like lint-staged's built-in concurrency/scheduling for CI to reduce execution time
  * The philosophies for the different tools vary. Many don't accept files and instead have their own notion of project. So I'd really like link-staged's distributed config files to run a tool in a non-root CWD, if any file of some type has changed in the that sub-directory. Rather than putting elaborate navigation into a root-level package.json file :hide:

Maybe I'm a snowflake, maybe I'm not. Currently I'm using "pre-commit" but I'd prefer lint-staged for its scriptability and per directory modularity. 

Has your stance changed since? 🤷‍♀️ 🙏

Edit: Alternatively, the "running lint-staged from node" APIs could let me provide a list of files
Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched
[]