chore: Change deprecation/deprecation to oxlint equivalent#21604
Merged
Conversation
Contributor
size-limit report 📦
|
d68bfc3 to
50c4210
Compare
nicohrubec
added a commit
that referenced
this pull request
Jun 18, 2026
#21604 enabled typescript/no-deprecated and added disable comments across the codebase but missed this vendored hapi usage, breaking lint on develop. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
48 tasks
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
2 participants
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.
Apparently
deprecation/deprecationdidn't work properly in oxlint. This PR enablestypescript/no-deprecatedand changed it everywhere.There were also 53 missing disabled lines, which I added in this commit: 42139b1