Skip to content
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

BigIntStats not actually exported from fs. #51674

Open
danfuzz opened this issue Feb 6, 2024 · 0 comments
Open

BigIntStats not actually exported from fs. #51674

danfuzz opened this issue Feb 6, 2024 · 0 comments
Labels
fs Issues and PRs related to the fs subsystem / file system.

Comments

@danfuzz
Copy link

danfuzz commented Feb 6, 2024

Version

v21.4.0

Platform

Darwin chug.lan 22.6.0 Darwin Kernel Version 22.6.0: Tue Nov 7 21:42:27 PST 2023; root:xnu-8796.141.3.702.9~2/RELEASE_ARM64_T8103 arm64

Subsystem

fs

What steps will reproduce the bug?

Shell command: node -e 'console.log(fs.BigIntStats)'

How often does it reproduce? Is there a required condition?

Always reproduces.

What is the expected behavior? Why is that the expected behavior?

I would expect this to output the usual representation of a class / constructor named BigIntStats, which is a class named in the documentation for the fs module, e.g. at https://nodejs.org/docs/latest/api/fs.html#class-fsstats under "bigint version."

(What I actually want to do is stuff like if (stats instanceof fs.BigIntStats) ....)

What do you see instead?

$ node -e 'console.log(fs.BigIntStats)'
undefined
$

Additional information

Compare to:

$ node -e 'console.log(fs.Stats)'
[Function: Stats]
$
@LiviaMedeiros LiviaMedeiros added the fs Issues and PRs related to the fs subsystem / file system. label Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fs Issues and PRs related to the fs subsystem / file system.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants