You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've got an issue with folder size calculation. We found out that stats.ino can be a BigInt when fs.lstat has additional options parameter.
I have 2 different files, one has ino = 57420895249767887n, the other has ino = 57420895249767888n
But after we cast BigInt to Number we could have the same result for 2 different values. Number(57420895249767887n) is equal to 57420895249767890
and Number(57420895249767888n) is equal to 57420895249767890 as well
Well, we have wrong size (results can be various because of Promise.all) if we call fs.lstat without {bigint: true} option.
Hi,
get-folder-size/index.js
Lines 59 to 61 in f5c7a3f
We've got an issue with folder size calculation. We found out that stats.ino can be a BigInt when fs.lstat has additional options parameter.
I have 2 different files, one has ino = 57420895249767887n, the other has ino = 57420895249767888n
But after we cast BigInt to Number we could have the same result for 2 different values.
Number(57420895249767887n)
is equal to57420895249767890
and
Number(57420895249767888n)
is equal to57420895249767890
as wellWell, we have wrong size (results can be various because of
Promise.all
) if we callfs.lstat
without{bigint: true}
option.Our current workaround:
The text was updated successfully, but these errors were encountered: