do we still want to maintain the package?

Question

do we still want to maintain the package?

aladdin-add opened this issue 3 years ago · comments

the package seems no longer necessary. As of now, something like npx has been increasingly popular.
TSC question: do we still want to maintain the package?

Brandon Mills · Answer 1 · Mon Oct 25 2021 11:50:00 GMT+0800 (China Standard Time)

Since npx is available with a default Node.js installation, we could add a note at the top of the docs suggesting npx eslint and then archive this repository to make it ready-only.

唯然 · Answer 2 · Sun Oct 31 2021 14:29:15 GMT+0800 (China Standard Time)

added "tsc agenda" label, to see if we can get consensus in the tsc meeting.

Nicholas C. Zakas · Answer 3 · Fri Nov 05 2021 03:54:48 GMT+0800 (China Standard Time)

Just as a reminder: when you add "tsc agenda" label, please also include a summary and a question.

唯然 · Answer 4 · Fri Nov 05 2021 10:49:56 GMT+0800 (China Standard Time)

@nzakas , I had edited the description, or should I leave a new comment?

唯然 · Answer 5 · Fri Nov 05 2021 12:37:35 GMT+0800 (China Standard Time)

Summary: the package seems no longer necessary. As of now, something like npx has been increasingly popular.
TSC question: do we still want to maintain the package?

Brandon Mills · Answer 6 · Wed Nov 17 2021 13:28:14 GMT+0800 (China Standard Time)

We agreed in the 2021-11-04 TSC meeting that we can stop maintaining this package now that npx is available. I will update any docs to direct users to npx instead and archive this repository.

Brandon Mills · Answer 7 · Mon Nov 22 2021 03:36:40 GMT+0800 (China Standard Time)

I didn't find any references to eslint-cli in the main eslint/eslint repository or eslint/website. In #18, I added a note to the top of this repository's readme recommending npx instead. Once that PR is approved and merged, I'll archive this repository.