[07:02:22] `Local logs : [07:02:23] npm ERR! code ERESOLVE [07:02:24] npm ERR! ERESOLVE unable to resolve dependency tree [07:02:26] npm ERR! [07:02:27] npm ERR! While resolving: video-cut-tool@0.5.0 [07:02:29] npm ERR! Found: react@18.2.0 [07:02:30] npm ERR! node_modules/react [07:02:32] npm ERR! react@"^18.2.0" from the root project [07:02:33] npm ERR! [07:02:35] npm ERR! Could not resolve dependency: [07:02:36] npm ERR! peer react@"^16.0.0" from @wikimedia/react.i18n@2.0.3 [07:02:38] npm ERR! node_modules/@wikimedia/react.i18n [07:02:39] npm ERR! @wikimedia/react.i18n@"^2.0.3" from the root project [07:02:41] npm ERR! [07:02:42] npm ERR! Fix the upstream dependency conflict, or retry [07:02:44] npm ERR! this command with --force, or --legacy-peer-deps [07:02:45] npm ERR! to accept an incorrect (and potentially broken) dependency resolution. [07:02:47] npm ERR! [07:02:48] npm ERR! See /home/punith/.npm/eresolve-report.txt for a full report. [07:02:50] [07:02:51] npm ERR! A complete log of this run can be found in: [07:02:53] npm ERR! /home/punith/.npm/_logs/2023-09-23T06_46_36_426Z-debug-0.log [07:02:54] [07:02:56] CI logs : https://integration.wikimedia.org/ci/job/generic-node16-browser-docker/4627/console [07:02:57] ` [07:02:59] Hello, we're encountering an error in our CI for the VideoCutTool project, and it seems to be related to the Wikimedia/react.i18n package. I'm working on this as part of GSOC and would like to know if the Wikimedia/react.i18n package is still being maintained. If it is, who can we reach out to for assistance in resolving this particular issue with the package? Your guidance and s [07:03:00] upport would be greatly appreciated. Thank you! [07:33:16] Punith Please read the pinned message [07:38:21] Google says: Last commit 3 years ago, main author david barratt. [07:38:21] [07:38:23] https://github.com/wikimedia/react.i18n [08:03:44] It might be useful to know: If it used to work earlier, what has changed now? [08:05:22] From the logs, the react version. The lib requires react v16, but the project is trying to use react 18 [08:06:26] It seems it has been like that for a long time, and the solution has been to provide the --legacy-peer-deps option