Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Mark as archived/broken more ESLint packages #257

Open
AlexWayfer opened this issue May 9, 2024 · 4 comments
Open

[BUG] Mark as archived/broken more ESLint packages #257

AlexWayfer opened this issue May 9, 2024 · 4 comments
Labels
badge Add or remove a badge from a package

Comments

@AlexWayfer
Copy link

fast-eslint is archived and non-working (sees no configuration while it's here, just outdated config formats): https://github.com/arnaud-dezandee/fast-eslint

eslint is broken: error after installation, last update was 10 years ago: https://github.com/iancmyers/atom-eslint

This 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.

@AlexWayfer AlexWayfer added the bug Something isn't working label May 9, 2024
@savetheclocktower
Copy link

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.

@AlexWayfer
Copy link
Author

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.

@confused-Techie
Copy link
Member

@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
Copy link
Author

@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.

@confused-Techie confused-Techie added badge Add or remove a badge from a package and removed bug Something isn't working labels Jul 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
badge Add or remove a badge from a package
Projects
None yet
Development

No branches or pull requests

3 participants