chore: upgrade @eslint/core
and @eslint/plugin-kit
#315
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.
This PR promotes
@eslint/core
to a runtime dependency and upgrades@eslint/core
and@eslint/plugin-kit
to the latest versions.This change ensures that
@eslint/markdown
will be used with a compatible version of@eslint/core
in dependent packages even if the core types are changed in a breaking way in the future. This will help avoiding bugs like #313 where the removal of a type from@eslint/[email protected]
to@eslint/[email protected]
was causing the TS build to fail. Since@eslint/core
was defined in the devDependencies, npm would not check its version range when@eslint/markdown
was itself installed as a dependency.I also made a change to the
tsconfig.json
in the type tests because I noticed that some files in thedist
directory were not being checked.