Maximilian Antoni

Thinking a bit more about this, it could also diff `npm-shrinkwrap.json` (or `package-lock.json` if present) from the previous release tag and the current state. This would also catch manual `npm...

I had the same thought. It could live behind a flag so that it's op-in. Would you like to look into this? I'm kind of unsure whether I'd like to...

I think `--contributors` is a good option name. I'd say the presence of the option means "enabled with defaults" and `--contributors AUTHORS.md` would set the filename. I like your suggested...

The value in adding contributors to `package.json` is that it honors the contributors in the distributed package. I thought npm might do something interesting with this information on their website,...

> `eslint_d: v14.0.3, bundled eslint: v9.8.0` This means that no local eslint was resolved and it falls back to the bundled version. Is there something wrong with the current working...

@piersolenski Can this be closed? Or do you think there's something wrong with `eslint_d`? If you're still experiencing issues, there's a new version with `--debug` support (see README). Maybe that...

Same issue twice after updating. Weirdly rebooting the machine fixed it for me. MacBook Air M1, latest OS.

Hm, I think the cause of this is npm cli directly depending on a different major version of `supports-color` than `chalk` and `debug`. I tried downgrading to `v7.x` in #7887...

That is something being requested for `eslint_d` as well here: https://github.com/mantoni/eslint_d.js/issues/236 It makes sense to put the core functionality into `core_d` so that it can be shared with this project...

This might also be a pattern that works for you and is already supported: https://github.com/sinonjs/sinon/pull/2538