-
Notifications
You must be signed in to change notification settings - Fork 12.3k
Make ESLint config compatible with Node 18/20 #5996
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
Conversation
|
WalkthroughThe ESLint configuration was updated to establish a Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
🔇 Additional comments (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Hi @prestoalvarez, the repository is using Node 22 (see) so I'm wondering why is this change needed. Is there any issue while using the repository in another project as a submodule? I can't think of another situation in which preserving compatibility with Node 18/20 makes sense. |
ernestognw
left a comment
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.
Let's not block this PR. If it works and we're using Node 22 it would only make it irrelevant for the CI.
Merging
import.meta.dirnamewithfileURLToPath(import.meta.url)to resolve.gitignorepath ineslint.config.mjs.import.meta.dirnameis Node 22+ only; it breaks linting on LTS Node 18/20 and in CI.