-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Implement missing node:fs
APIs
#18218
Comments
i noticed that |
symlink is unstable https://doc.deno.land/builtin/unstable#Deno.symlink |
see #7666 |
Some of these have now been implemented, here's an updated checklist: (Update(@kt3k): Removed the list of APIs with checkboxes here. We keep updating the list above) |
I would grab some, for a start I would go with mkdtemp/mkdtempSync. Anybody already on the case? |
may i work on this issue? |
@F3n67u yes, please do |
please reference this issue in any PRs you're gonna create |
@AliBasicCoder ok, I will |
@AliBasicCoder I tried to implement |
I'll work on |
Implementing (I'm rewriting a port of a Node.js framework and I need this func for |
I believe the following are required from the Deno FS API to be implemented:
Is this correct? |
I guess the last 2 could be polyfilled if we don't mind the performance |
@kt3k should this still be in |
node:fs
APIs
Part of #18218. Implements `fs.readv` and `fs.readvSync` and enables the corresponding `node_compat` tests.
Part of #18218. Implements `fs.readv` and `fs.readvSync` and enables the corresponding `node_compat` tests.
Ref #21260 |
Another possible reason to add |
Part of #18218 - Adds `fs.lutimes` and `fs.lutimesSync` to our node polyfills. To do this I added methods to the `FileSystem` trait + ops to expose the functionality to JS. - Exports `fs._toUnixTimestamp`. Node exposes an internal util `toUnixTimestamp` from the fs module to be used by unit tests (so we need it for the unit test to pass unmodified). It's weird because it's only supposed to be used internally but it's still publicly accessible - Matches up error handling and timestamp handling for fs.futimes and fs.utimes with node - Enables the node_compat utimes test - this exercises futimes, lutimes, and utimes.
Part of denoland#18218 - Adds `fs.lutimes` and `fs.lutimesSync` to our node polyfills. To do this I added methods to the `FileSystem` trait + ops to expose the functionality to JS. - Exports `fs._toUnixTimestamp`. Node exposes an internal util `toUnixTimestamp` from the fs module to be used by unit tests (so we need it for the unit test to pass unmodified). It's weird because it's only supposed to be used internally but it's still publicly accessible - Matches up error handling and timestamp handling for fs.futimes and fs.utimes with node - Enables the node_compat utimes test - this exercises futimes, lutimes, and utimes.
) Closes denoland#21260. Part of denoland#18218. Implements `node:fs.lchown`, and enables the node_compat test for it. The test uses `process.getegid`, which we didn't have implemented, so I went ahead and implemented that as well to get the test working.
Just one left, closing in favor of #26020. |
Current status: 52/58
The text was updated successfully, but these errors were encountered: