chore: introducing @e18e/eslint-plugin - #23357
Conversation
| const moduleId = meta.id | ||
|
|
||
| const importee = callstack[callstack.length - 1] | ||
| const importee = callstack.at(-1) |
There was a problem hiding this comment.
#12539 (review) Follow the previous expectations
|
I think we'd also need to double check the performance but I suppose most is fine. Except maybe It'll also be a bit tricky if we integrate this and have to migrate to oxlint later, but not a big reason to hold this PR off if all looks fine. |
I will add an API performance comparison example later. yes,
Perhaps we can consider this together when we migrate to oxlint? |
|
I think some quick performance tests is fine and I'll trust what you discover 😄 I don't think we need to wait for oxlint, but I'll leave to @sapphi-red if he wants to hold it off or something. If the changes here doesn't cause big perf issues, I think we can merge it now. For me particularly I'm interested in the perf of |
Co-authored-by: Bjorn Lu <bjornlu.dev@gmail.com>
|
I did a simple test in a Node.js environment, and the performance of the spread operator and The differences between Therefore, concat vs spread(combined array) concat vs spread(single item) |
Introducing the e18e/eslint-plugin, discarding some old syntax, and replacing it with new APIs and syntax supported by Node 20+. https://github.com/e18e/eslint-plugin#rules