@codebytere done

Btw, why asar file returns always size "0"?

Because, if i call native fs.lstat, will be returned correct size, ino, etc.

fs.lstat('app.asar', console.log)
> null Stats {
  dev: 0,
  mode: 33206,
  nlink: 1,
  uid: 0,
  gid: 0,
  rdev: 0,
  blksize: 4096,
  ino: 7881299348490233,
  size: 132247133,
  blocks: 258296,
  atimeMs: 1750337668594.9424,
  mtimeMs: 1750337664266.7073,
  ctimeMs: 1750337664266.7073,
  birthtimeMs: 1750337663840.4016
}

#47505 (comment)

https://www.electronjs.org/docs/latest/tutorial/asar-archives#fake-stat-information-of-fsstat

Any progress with this?

@panther7 we're down a few maintainers due to illness at the moment. Please be patient. This PR will be reviewed as bandwidth permits.

Another month has out, can I help with it some progress?

Next month out.

Three months of being ignoring. What can i do for move this PR to merge?

@codebytere

Ok, this can't works, becase return object must be a type BigIntStats (if bigint is sets to true).
BigIntStats hasn't constructor.
This "asar" hack is bad solution.

Ok, this can't works, becase return object must be a type BigIntStats (if bigint is sets to true).
BigIntStats hasn't constructor.
This "asar" hack is bad solution.

@panther7 can you clarify what you mean here? Are you saying your currently proposed change won't work?

@jkleinsc

Yes, it won't work because the fs.stat method with the parameter bigint = true must return a BigIntStats object, which is not possible because Electron uses "fake" Stats which returns artificial values ​​for the asar file.

Since BigIntStats doesn't have a constructor like Stats, it can't be solved.

The only option is to "cancel" fake Stats (which is deprecated by the way), but someone would have to comment on that, who did it and why.

I know, how fix it but I don't know, why maintaner use fake Stats for asar file. Maybe some @MarshallOfSound?

@ckerr @jkleinsc

@panther7 what does 'fake stats' mean here? i.e. what part of the code are you referring to?

@ckerr
I mean this:

Using deprecated Stats construtor which is deprecated and will be probably remove in Nodejs 24 or 26.

For resolve this issue is need BigIntStats object as result if bigint: true option sets. But BigIntStats hasn't construtor.

Right solution is use native fs.stat method which return right object. But i don't know, why is used this fake Stats.

This is probably fix 0626af3 with using native lstat...

@panther7 just to make sure I'm understanding the PR correctly -- the other properties returned by lstatSync, e.g. size, will already be a BigInt and that's why we don't need size in the new Object.entries({}) call, correct?

Actually, fs.lstat with the bigint option is broken in Electron. The expected result is a BigIntStats object with bigint values.

The question is: why are Electron developers creating a fake Stats object with zero size and other fake attributes?

My suggested solution is to use native fs.lstat, which returns the correct object type (Stats or BigIntStats).

If a fake Stats object is not necessary, native fs.lstat should be used by default.

Used Stats contructor is deprecated from NodeJS 20.

@ckerr

The question is: why are Electron developers creating a fake Stats object with zero size and other fake attributes?

Looks like that new Stats code was added in #24495. There was some code review discussing the fake attributes:

stats.atime and friends are never actually set, so this always returns fakeTime

Trying to avoid changing implementation during ts stuff, also why I had to type a few things as any. Turns our there's a lot of inaccuracies in this file. They can all be addressed individually once this has landed.

Maybe @MarshallOfSound could tell about it.