ci: Update CI to run oxlint/oxfmt instead of ESLint/Prettier - #1880
ci: Update CI to run oxlint/oxfmt instead of ESLint/Prettier#1880joker23 wants to merge 2 commits into
Conversation
a51a8b8 to
e933a80
Compare
e933a80 to
606955c
Compare
|
@launchdarkly/browser size report |
1 similar comment
|
@launchdarkly/browser size report |
c3e23cb to
7acf412
Compare
7acf412 to
72b4299
Compare
|
@launchdarkly/js-sdk-common size report |
|
@launchdarkly/js-client-sdk-common size report |
|
@launchdarkly/js-client-sdk size report |
…fiers The rule appears to misfire on bare npm package specifiers (which never take a file extension) in contract-test-utils. Suppressed with a comment to revisit the rule config later.
72b4299 to
b7cb577
Compare
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
1 participant
This PR will enable oxfmt in the CI and convert some eslint ignore comments to oxlint format - currently, we are not failing the build due to formatting errors (we will run the formatter in a later PR)
Note
Overview
Extends the shared composite CI action with a Format Check step that runs each workspace’s
format:checkscript (oxfmt--check), placed after lint and before tests.That step uses
continue-on-error: trueso formatting drift does not block merges while the repo is still migrating to oxfmt; the TODO notes removing that once reformatting is complete.In contract-test-utils, adds targeted
oxlint-disable-next-line import/extensionscomments (with notes to revisit rule config) on imports from bare package names—body-parser,cors,express,ws, and LaunchDarkly SDK packages—so oxlint’s extension rule does not false-positive on those paths.Reviewed by Cursor Bugbot for commit b7cb577. Bugbot is set up for automated code reviews on this repo. Configure here.