chore: try oxlint jsPlugins with angular-eslint#2223
Conversation
|
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2223 +/- ##
=======================================
Coverage 100.0% 100.0%
=======================================
Files 198 198
Lines 17998 17998
Branches 4995 4995
=======================================
Hits 17998 17998
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
angular-slickgrid
aurelia-slickgrid
slickgrid-react
slickgrid-vue
@slickgrid-universal/binding
@slickgrid-universal/common
@slickgrid-universal/composite-editor-component
@slickgrid-universal/custom-footer-component
@slickgrid-universal/custom-tooltip-plugin
@slickgrid-universal/empty-warning-component
@slickgrid-universal/event-pub-sub
@slickgrid-universal/excel-export
@slickgrid-universal/graphql
@slickgrid-universal/odata
@slickgrid-universal/pagination-component
@slickgrid-universal/row-detail-view-plugin
@slickgrid-universal/rxjs-observable
@slickgrid-universal/text-export
@slickgrid-universal/utils
@slickgrid-universal/vanilla-bundle
@slickgrid-universal/vanilla-force-bundle
commit: |
|
Did you find that |
|
@overlookmotel yes it works with your suggestion in that same oxc github issue which you suggested to separate the linting into 2 tasks (which is what I did in this PR):
So I'll use that approach for now until #2223 is fixed. oxlint is so damn fast anyway that even with 2 passes, it's not even comparable with eslint. So I'm ok with this approach, it's slightly more code and time but it works and it's awesomely fast, so I'm good for now 🚀 Note that my code was already linted from my previous eslint setup and I haven't really tried to change some code to verify that the jsPlugins does work. I think I had 1 or 2 warnings with oxlint, but I could verify more in depth if that is what you were asking to confirm? |
|
Thanks for coming back. When you have time, if you're able to put it through its paces a bit and report any problems, that'd be a huge help. My next task is to build a plugin tester, but it turns out it's not really possible to automate because every repo uses different testing libraries etc, so I'll need to test plugins on a case-by-case basis - very laborious. In meantime, bug reports (or even "it works 🚀!") is really helpful. If we can find bugs, they'll probably not be too hard to fix. The tricky part is hunting them down! |
|
@overlookmotel hey sorry for the delay, I just made a quick test and yes Thanks for the great work and amazing perf 🚀
|
|
Thanks very much for testing it and coming back to me. Really appreciate it. |
|
OOM bug on Windows was fixed in oxc-project/oxc#17013, which is in Oxlint 1.34.0, released last night. Would massively appreciate feedback to confirm that the fix does indeed work. If it doesn't, please let us know on oxc-project/oxc#14375. |

try using oxlint with
"jsPlugins": ["@angular-eslint/eslint-plugin"]for theframeworks/angularproject.On windows I'm getting this error, let see if it works in CI with Ubuntu
Edit
I think I'll use the temporary suggestion provided in the OXC issue on Windows. I'll revisit it later when the issue is fixed.