Npm install failure after recent dependency upgrade
envgap__apache__incubator-seata-7855
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
2aa4b5772cafb7aaec5ad08c101ae8a5544fbd37- Manifest
console/src/main/resources/static/console-fe/package.json- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
apache/incubator-seata #7855 · read the original issue
### Check Ahead - [x] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. - [ ] I am willing to try to fix this bug myself. ### Ⅰ. Issue Description After merging [this PR](https://github.com/apache/incubator-seata/pull/7849), npm install started failing unexpectedly. We need to check whether any of the newly upgraded dependencies are conflicting with existing ones and consider possible solutions. ### Ⅱ. Describe what happened See https://github.com/apache/incubator-seata/actions/runs/20189509945/job/57966627142 ### Ⅲ. Describe what you expected to happen _No response_ ### Ⅳ. How to reproduce it (as minimally and precisely as possible) _No response_ ### Ⅴ. Anything else we need to know? _No response_ ### Ⅵ. Environment _No response_
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]