-
-
Notifications
You must be signed in to change notification settings - Fork 435
Description
Describe the bug
There's problem with recognize promise which are return from fs-extra for couple of functions.
Another one:
Interesting thing is, that happend only for WebStorm, VSCode doesn't complaining.
I was trying to fix it in #2015 but this solution isn't good and i reverted it.
Let's see here, typescript doesn't complain:
https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAMwM6KhEcDkyC0BTADxigENMBuAKEoGMIA7JeMEqJPAYQAsT6BzPABsIfALKsA1gBMIAd3pwAvHAAUdejDwakALjhMowfgEolAPlUBvSnFtwoQvCXa64AbWt2vcAG542wAx6mJgANDbetgBGEFIAnsGYEbYAvgC6lCnG1OpMcJb2js54KClKcCSyJMDwyBEAdA4kUgBiwIJ4KiGhWACuMAgAHJjZtvUwXFoqLGycPPxCIuJQ0nL0o3D1NCQwNFwqKqaKFioFDh3Frm5pcFnGVBG5EB31wnwq504u90A
PS: I see there's a problem also here, for non related package:
packages/i18n/__tests__
Steps to reproduce
- Let's run project on WebStorm
- Run
pnpm i - Check warnings on built in console
System Info
System:
OS: Windows 11 10.0.26200
CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor
Memory: 18.17 GB / 31.91 GB
Binaries:
Node: 25.1.0
npm: 11.6.2
pnpm: 10.15.1
bun: 1.3.3
Browsers:
Chrome: 143.0.7499.170
Edge: Chromium (140.0.3485.54)
Firefox: 144.0
Internet Explorer: 11.0.26100.7309
npmPackages:
wxt: workspace:* => 0.20.13Used Package Manager
pnpm
Validations
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
