-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fs.statAsync should not be defined globally #3466
Labels
Comments
matz3
added a commit
to matz3/karma
that referenced
this issue
Apr 9, 2020
Defining fs.statAsync affects other modules such as bluebird which throws an error because of the 'Async'-suffix: > Cannot promisify an API that has normal methods with 'Async'-suffix > See http://goo.gl/MqrFmX Fixes: karma-runner#3466
johnjbarton
pushed a commit
that referenced
this issue
Apr 9, 2020
Defining fs.statAsync affects other modules such as bluebird which throws an error because of the 'Async'-suffix: > Cannot promisify an API that has normal methods with 'Async'-suffix > See http://goo.gl/MqrFmX Fixes: #3466
🎉 This issue has been resolved in version 5.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
anthony-redFox
pushed a commit
to anthony-redFox/karma
that referenced
this issue
May 16, 2023
Defining fs.statAsync affects other modules such as bluebird which throws an error because of the 'Async'-suffix: > Cannot promisify an API that has normal methods with 'Async'-suffix > See http://goo.gl/MqrFmX Fixes: karma-runner#3466
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
There seems to be a problem with karma v5.0.0 that is caused by the fact karma defines
fs.statAsync
(actuallygraceful-fs
).Other projects that still use bluebird seem to crash now. In this case our
karma-ui5
plugin internally usescacache
(viapacote
), which loads bluebird.I did not fully debug the actual issue, but in general I would not expect karma to extend/modify API of another module, as this likely affects other code running within the same process.
I've created a PR to fix this issue: #3467
The text was updated successfully, but these errors were encountered: