build(deps-dev): replace standard with neostandard #340
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsumners
approved these changes
Nov 27, 2024
This was referenced Nov 28, 2024
This was referenced Dec 8, 2024
This was referenced Dec 8, 2024
This was referenced Dec 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The main fastify repo migrated from standard to neostandard with fastify/fastify#5509, so the rest of the repos should (neo)standardise around this and use the same linting tool. At present we have a mishmash of standard, eslint with custom rules and various plugins, and prettier across the plugin repos.
Checklist
npm run testandnpm run benchmarkand the Code of conduct