-
Notifications
You must be signed in to change notification settings - Fork 15.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Remove statSyncNoException
for good
#15092
Conversation
lib/common/asar.js
Outdated
fs.statSyncNoException = pathArgument => { | ||
const { isAsar, asarPath, filePath } = splitPath(pathArgument) | ||
if (!isAsar) return statSyncNoException(pathArgument) | ||
if (!isAsar) return fs.statSyncNoException(pathArgument) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MarshallOfSound I'm actually not quite sure what this code is supposed to do. This would is just recursion, right?
statSyncNoException
for good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@felixrieseberg rip, see #15089; we already removed it from the fork but forgot to remove it here 🙃
ty for this
Release Notes Persisted
|
We have automatically backported this PR to "4-0-x", please check out #15110 |
Description of Change
The existing code throws if anasar
is used. This simply changes the assignment, ensuring that the correct object is returned.New plan: Let's just cut
fs.statSyncNoException
for real.Checklist
npm test
passesRelease Notes
Notes: Fix "TypeError: statSyncNoException is not a function" when asar is used