[Snyk] Upgrade @typescript-eslint/parser from 6.4.1 to 8.8.1 #366
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.
Snyk has created this PR to upgrade @typescript-eslint/parser from 6.4.1 to 8.8.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 822 versions ahead of your current version.
The recommended version was released on 24 days ago.
Release notes
Package name: @typescript-eslint/parser
8.8.1 (2024-10-07)
🩹 Fixes
node --eval
script (#10098)❤️ Thank You
You can read about our versioning strategy and releases on our website.
8.8.0 (2024-09-30)
🚀 Features
🩹 Fixes
export type *
in d.ts to support TS<5.0 (#10070)isBuiltinSymbolLikeRecurser()
(#10026)❤️ Thank You
You can read about our versioning strategy and releases on our website.
8.7.0 (2024-09-23)
🚀 Features
export *
exports to see if all exported members are types (#10006)🩹 Fixes
getStaticMemberAccessValue
(#10004)NewExpression
as a parent ofSpreadElement
(#10024)❤️ Thank You
You can read about our versioning strategy and releases on our website.
8.6.0 (2024-09-16)
🚀 Features
allow
option forrestrict-template-expressions
(#8556)🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.