Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
66 changes: 33 additions & 33 deletions quickwit/quickwit-ui/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,48 +5,48 @@
"private": true,
"packageManager": "yarn@1.22.22",
"dependencies": {
"@babel/core": "7.29.6",
"@babel/runtime": "7.28.6",
"@biomejs/biome": "2.4.4",
"@dr.pogodin/babel-plugin-transform-assets": "1.2.6",
"@babel/core": "8.0.7",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Retain Babel 7 while using the React App preset

The Jest configuration runs every transformed test file through babel-preset-react-app@10.1.0, whose locked preset and plugin suite targets Babel 7 and asserts that major version. Selecting Babel core 8 here causes those plugins to reject the loaded core during yarn --cwd quickwit-ui test, so the UI unit-test job cannot run; keep core 7 or replace the preset and plugins with Babel 8-compatible versions.

Useful? React with 👍 / 👎.

"@babel/runtime": "8.0.7",
"@biomejs/biome": "2.6.2",
"@dr.pogodin/babel-plugin-transform-assets": "2.0.0",
"@emotion/react": "11.14.0",
"@emotion/styled": "11.14.1",
"@monaco-editor/react": "4.7.0",
"@mui/icons-material": "7.3.8",
"@mui/lab": "7.0.1-beta.22",
"@mui/material": "7.3.8",
"@mui/system": "7.3.8",
"@mui/x-charts": "8.27.0",
"@mui/x-date-pickers": "8.27.2",
"@testing-library/dom": "10.4.1",
"@testing-library/jest-dom": "6.9.1",
"@testing-library/react": "16.3.2",
"@testing-library/user-event": "14.6.1",
"@mui/icons-material": "9.5.0",
"@mui/lab": "7.0.1-beta.25",
"@mui/material": "9.5.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Migrate removed Material UI APIs before upgrading

Material UI 9 removes APIs that this UI still relies on: IndexSideBar.tsx passes the removed TextField.InputProps and reads the obsolete params.InputProps, while components such as Loader.tsx and TimeRangeSelect.tsx use removed Box system props like display, p, and flexGrow. The type-check therefore reports invalid props, and builds that skip type-checking lose the affected adornment and layout styling; apply the official v9 migrations alongside this major-version bump.

Useful? React with 👍 / 👎.

"@mui/system": "9.5.0",
"@mui/x-charts": "9.16.0",
"@mui/x-date-pickers": "9.16.0",
"@testing-library/dom": "10.4.2",
"@testing-library/jest-dom": "7.0.1",
"@testing-library/react": "16.3.3",
"@testing-library/user-event": "14.6.8",
"@types/jest": "30.0.0",
"@types/node": "26.6.4",
"@types/react": "19.2.14",
"@types/react-dom": "19.2.3",
"@types/node": "26.6.5",
"@types/react": "19.3.0",
"@types/react-dom": "19.3.0",
"@types/swagger-ui-react": "5.18.0",
"babel-jest": "30.2.0",
"babel-jest": "30.5.2",
"babel-preset-react-app": "10.1.0",
"dayjs": "1.11.19",
"jest": "30.2.0",
"jest-environment-jsdom": "30.2.0",
"monaco-editor": "0.55.1",
"react": "19.2.4",
"dayjs": "1.11.23",
"jest": "30.5.2",
"jest-environment-jsdom": "30.5.2",
"monaco-editor": "0.57.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Update Monaco imports for the reorganized entry points

Monaco 0.56 reorganized its ESM exports, but EditorProvider.tsx and QueryEditor.tsx still import monaco-editor/esm/vs/editor/editor.api. Under 0.57's export map that legacy subpath no longer resolves, so both the type-check and Vite build fail before the editors can be bundled; switch those imports to the supported monaco-editor/editor entry point described in the official changelog.

Useful? React with 👍 / 👎.

"react": "19.3.1",
"react-app-polyfill": "3.0.0",
"react-dom": "19.2.4",
"react-number-format": "5.4.4",
"react-router": "7.18.2",
"styled-components": "6.1.19",
"react-dom": "19.3.1",
"react-number-format": "5.4.5",
"react-router": "8.5.0",
"styled-components": "6.6.0",
"styled-icons": "10.47.1",
"swagger-ui-react": "5.32.14",
"typescript": "5.9.3",
"vite": "7.3.7"
"swagger-ui-react": "5.34.0",
"typescript": "7.0.2",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep TypeScript compatible with the checked-in tsconfig

The UI config still sets moduleResolution to node, the deprecated node10 alias that TypeScript 6 reports will stop functioning in TypeScript 7. Consequently, the yarn --cwd quickwit-ui type step in .github/workflows/ui-ci.yml fails after this upgrade; migrate the config to a supported resolution mode such as bundler or retain a compatible TypeScript version.

Useful? React with 👍 / 👎.

"vite": "8.3.5"
},
"resolutions": {
"@types/react": "19.2.14",
"@types/react-dom": "19.2.3",
"@types/react": "19.3.0",
"@types/react-dom": "19.3.0",
"@babel/plugin-transform-modules-systemjs": "7.29.4",
"dompurify": "3.4.14",
"glob": "11.1.0"
Expand All @@ -62,6 +62,6 @@
"e2e-test": "playwright test"
},
"devDependencies": {
"@playwright/test": "^1.63.0"
"@playwright/test": "^1.64.1"
}
}
Loading
Loading