fix: add missing nanosecond-precision properties to Stats #943
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
uhyo
changed the title
G-Rath
changed the title
G-Rath
approved these changes
Sep 15, 2023
github-actions bot
pushed a commit
that referenced
this pull request
Sep 15, 2023
## [4.2.3](v4.2.2...v4.2.3) (2023-09-15) ### Bug Fixes * add missing nanosecond-precision properties to Stats ([#943](#943)) ([b9d4c6d](b9d4c6d))
|
🎉 This PR is included in version 4.2.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello, I use memfs for writing unit tests for file system-related Node.js code. I recently noticed that the current implementation of
Statslacks nanosecond-precision properties (atimeNs, etc.) compared to Node.js one.This PR adds those properties for better compatibility.
fixes #775 (not sure why it has been closed though)