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.
feat: add @nkzw/oxlint-config for stricter linting #696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
feat: add @nkzw/oxlint-config for stricter linting #696
Changes from all commits
727ed6eFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Disabling the
no-undefrule for the entire project can be risky as it might hide legitimate bugs caused by typos or forgotten imports. A safer approach would be to declare the expected globals where they are used.While
oxlint.config.tsmight not support aglobalskey,oxlint(and ESLint) respects inline global declarations. For files that use Node.js globals likeBufferorprocess, you could add a comment at the top of the file:/* globals Buffer, process */This would allow you to re-enable the
no-undefrule (or set it towarn), providing better protection against undefined variables. Please consider this alternative approach for enhanced safety.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: node-modules/urllib
Length of output: 689
🏁 Script executed:
Repository: node-modules/urllib
Length of output: 290
🏁 Script executed:
Repository: node-modules/urllib
Length of output: 763
🏁 Script executed:
Repository: node-modules/urllib
Length of output: 4693
🏁 Script executed:
Repository: node-modules/urllib
Length of output: 1741
🏁 Script executed:
Repository: node-modules/urllib
Length of output: 768
🏁 Script executed:
Repository: node-modules/urllib
Length of output: 305
ESLint suppress comment won't prevent Biome from flagging the control-character regex
Line 6's ESLint disable applies only to ESLint, not Biome. Since
noControlCharactersInRegexis enabled in biome.json's recommended rules, the\u0000escape will still trigger a linting error. Use a Unicode property escape instead:Proposed change
This regex is functionally equivalent, compatible with the project's ES2022 target and Node.js 18.19.0+ requirement, and will not trigger linting errors.
📝 Committable suggestion
🧰 Tools
🪛 Biome (2.4.6)
[error] 6-6: Unexpected control character in a regular expression.
(lint/suspicious/noControlCharactersInRegex)
🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.