Open AlexWayfer opened 1 month ago
I still use linter-eslint-node
(installed directly from the repo, I think) and my feeling is that it'll eventually move to Pulsar Cooperative and live in that repo. (Not looking forward to changing the name.) Try it out and let me know if it doesn't work for you.
But, yeah, the other packages listed are worth marking as broken.
Yeah, I've installed linter-eslint-node
from official repos and it works, even with the newest versions of ESLint and its config.
Probably, we should update the package page and remove "Archived" badge.
@AlexWayfer But the repository where the code lives is still archived. That's all the badge is intended to indicate, so we will probably want to go ahead and leave it, even if the package is still working
@AlexWayfer But the repository where the code lives is still archived. That's all the badge is intended to indicate, so we will probably want to go ahead and leave it, even if the package is still working
Yeah, I mean the fork, which you've mention, probably should replace this package, or be added as a new one into official repos, without this badge.
fast-eslint
is archived and non-working (sees no configuration while it's here, just outdated config formats): https://github.com/arnaud-dezandee/fast-eslinteslint
is broken: error after installation, last update was 10 years ago: https://github.com/iancmyers/atom-eslintThis issue is a successor of #244, so we have no ESLint integration with Pulsar Editor right now.
I saw
linter-eslint-node
fork by @savetheclocktower, but it's not in maintenance.