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.

Sign up for GitHub

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

Jump to bottom

should we stop using standardjs and instead use some other lint ? #11

Open
rom1504 opened this issue May 29, 2023 · 2 comments
Open

should we stop using standardjs and instead use some other lint ? #11

rom1504 opened this issue May 29, 2023 · 2 comments

Comments

@rom1504
Copy link
Member

rom1504 commented May 29, 2023

NO
standardjs provides

  • constantly updated lint rules
  • easy to apply via npm run fix
  • no need to debate on specific rules
@rom1504 rom1504 transferred this issue from PrismarineJS/prismarine-meta Jun 3, 2023
@hvlxh
Copy link

hvlxh commented Jun 4, 2023 •
edited
Loading

i would use eslint with standardjs code-style. eslint has vscode extensions to see errors in code editor instead of using eslint . in terminal

@rom1504
Copy link
Member Author

rom1504 commented Jun 4, 2023

Standardjs is integrated with vscode

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rom1504 @hvlxh