chore(deps-dev): bump neostandard to 0.14.0-next.1 and eslint to v10 - #41
Draft
Puppo wants to merge 2 commits into
Draft
chore(deps-dev): bump neostandard to 0.14.0-next.1 and eslint to v10#41Puppo wants to merge 2 commits into
Puppo wants to merge 2 commits into
Conversation
added 2 commits
August 19, 2026 15:47
Fastify 5+ hardcodes QUERY in supportedMethods at instance creation, so the plugin's first-registration guard is unreachable in the current test environment. The guard is kept for future Fastify versions / custom environments where QUERY may not yet be registered, and is now marked with c8 ignore comments so the 100% coverage threshold is met.
- neostandard ^0.13.0 -> 0.14.0-next.1 (exact pin; first neostandard release with ESLint 10 support) - eslint ^9.17.0 -> ^10.0.0 - Add engines.node field documenting the new Node floor No source changes: eslint.config.js already uses the named resolveIgnoresFromGitignore export and the ts / ignores factory options, both still supported in 0.14. Note: neostandard@0.14 raises the Node.js floor to ^22.13.0 || >=24. The Node 20 row in CI is intentionally kept and will fail lint — this is expected. Local developers on Node 20 will also see pre-commit lint failures until they upgrade. Follow-up: when stable 0.14.0 is published, relax the exact pin back to ^0.14.0.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Upgrades
neostandardto0.14.0-next.1(the first release on thenextdist-tag with ESLint 10 support) and bumpseslintto^10.0.0. Also adds anengines.nodefield documenting the new Node floor.Changes
neostandard:^0.13.0→0.14.0-next.1(exact pin)eslint:^9.17.0→^10.0.0engines.node: ^22.13.0 || >=24(advisory; documents the new neostandard floor)A separate commit (
test: mark unreachable QUERY pre-registration branch as c8-ignored) marks the plugin'sif (!fastify.supportedMethods.includes(QUERY_METHOD))guard withc8 ignorecomments — Fastify 5+ hardcodes QUERY insupportedMethodsat instance creation, making that branch unreachable in the current test environment. The guard is kept for future Fastify versions / custom environments where QUERY may not yet be registered.Why no source changes
eslint.config.jsalready uses the namedresolveIgnoresFromGitignoreexport and thets/ignoresfactory options, both still supported in 0.14. The 0.14 breaking changes (ESM-only, scoped configs, removed React logic rules, deprecated default-export property access) do not touch this file's shape.Heads-up: Node 20 will fail lint
neostandard@0.14requires Node^22.13.0 || >=24. The Node 20 row in CI is intentionally kept per maintainer decision and will fail lint by design. Local developers on Node 20 will also see pre-commit lint failures until they upgrade.Follow-up
When stable
0.14.0is published, relax the exact pin back to^0.14.0. Tracked by exact-pin notation only — Dependabot won't auto-bump pre-release pins.