-
Notifications
You must be signed in to change notification settings - Fork 47
Issues: npm/write-file-atomic
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[BUG] Class private methods are not enabled. Please add @babel/plugin-proposal-private-methods to your configuration.
Bug
thing that needs fixing
Needs Triage
needs an initial review
#163
opened May 23, 2023 by
sibelius
1 task done
The final thing that needs fixing
Needs Triage
needs an initial review
fsync
makes it 16 times slower
Bug
#155
opened Mar 30, 2023 by
davidfirst
1 task done
[BUG] Does not handle thing that needs fixing
undefined
return value from signal-exit's onExit() function
Bug
#84
opened Oct 2, 2021 by
kayahr
writeFileSync
may error with cross-device link not permitted
on Windows
#71
opened Oct 12, 2020 by
davidmurdoch
[BUG] The temporary file name is longer than the target file name
Bug
thing that needs fixing
#63
opened Jun 3, 2020 by
zkochan
[FEATURE] Restore creation date of updated file
Enhancement
new feature or improvement
#60
opened Apr 10, 2020 by
philippkuehn
[BUG] <The library seems to not be safe with multiple webworkers>
Bug
thing that needs fixing
#57
opened Jan 29, 2020 by
oltreseba
EPERM error on Windows when multiple processes try to write the same file
#28
opened Oct 8, 2017 by
asapach
ProTip!
Follow long discussions with comments:>50.