kaxil commented on code in PR #77219:
URL: https://github.com/apache/airflow/pull/77219#discussion_r4607189565


##########
airflow-core/src/airflow/ui/package.json:
##########
@@ -89,35 +88,29 @@
     "@types/react-dom": "^19.3.0",
     "@types/react-syntax-highlighter": "^15.5.13",
     "@typescript-eslint/eslint-plugin": "^8.72.1",
-    "@typescript-eslint/parser": "^8.72.1",
     "@typescript-eslint/utils": "^8.72.1",
     "@vitejs/plugin-react": "^6.3.0",
     "@vitest/coverage-v8": "^5.1.0",
     "babel-plugin-react-compiler": "^1.0.0",
-    "eslint": "^10.11.0",
     "eslint-plugin-i18next": "^6.1.5",
-    "eslint-plugin-jsx-a11y": "^6.10.2",
-    "eslint-plugin-oxlint": "1.90.0",
     "eslint-plugin-perfectionist": "^5.12.1",
     "eslint-plugin-react": "^7.37.5",
-    "eslint-plugin-react-hooks": "^7.1.1",
-    "eslint-plugin-react-refresh": "^0.5.7",
     "eslint-plugin-unicorn": "^76.0.0",
     "globals": "^17.14.0",
     "happy-dom": "^21.0.4",
     "msw": "^3.0.4",
     "openapi-merge-cli": "^2.0.3",
     "oxfmt": "0.78.0",
     "oxlint": "1.93.0",
+    "oxlint-tsgolint": "7.0.2006",
     "ts-morph": "^27.0.2",
     "typescript": "^6.0.3",
-    "typescript-eslint": "^8.72.1",
     "vite": "^8.3.7",
     "vite-plugin-css-injected-by-js": "^5.0.3",
     "vitest": "^5.1.0",
     "web-worker": "^1.5.0"
   },
-  "packageManager": "[email protected]",
+  "packageManager": "[email protected]",

Review Comment:
   `basic-tests.yml` and `ui-e2e-tests.yml` still set up pnpm with `version: 
9`, so CI installs and tests this UI on pnpm 9 (the React UI tests job on this 
PR logs it). Should those two switch to `package_json_file: 
airflow-core/src/airflow/ui/package.json`, like the ts-sdk jobs? Fine as a 
follow-up, since both only run `--frozen-lockfile` and can't bring the `libc` 
churn back.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to