-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
Improve the fs module, add new methods/functions (mkfifo, mknod) #38344
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
Comments
A few questions:
|
Im not sure if i understand you correctly, but there are methods/operations: Can you clarify (give me a example) what are a "POSIX operation" is?
Indeed, this would only work for Unix/Linux/*nix based OSs. |
This comment has been minimized.
This comment has been minimized.
POSIX is a family of standards that most OSes follow (GNU/Linux, Unix and Unix-like), the neat thing about POSIX is you can use the same implementation everywhere and expect it to work (well we'd still need to make a Windows-specific implementation I guess). If those operations are not defined by a POSIX standard, I'm not sure it's reasonable for us to make a cross-platform API given the number of platforms Node.js supports. |
I was confused by the term "operation". Windows has also "named pipes": https://docs.microsoft.com/en-us/windows/win32/ipc/named-pipes In python (https://docs.python.org/3/library/os.html#os.mkfifo, see "Availability"), if you use the "os" module, its common that some methods are not exists if you switch to/from windows/linux. |
We already have macOS specific fs operations for some reason (E.G.: https://nodejs.org/api/fs.html#fs_fspromises_lchmod_path_mode), so yeah, it's worth considering integrating it without Windows support as a first step. Since those are indeed POSIX features (sorry I read the wrong man page at first), we might be able to implement it in a cross-platform way. Leaving Windows support aside, would you be interested on working on an implementation? |
Interested, of course. But i dont think im not the right person for this. |
Generally speaking we tend to rely on abstracted implementations of file system functions provided by the libuv dependency. For any new fs functions the discussion should start there (https://github.com/libuv/libuv) |
To help your feature request finding volunteers, I recommend create two separate issues on the libuv repo: one for |
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment. For more information on how the project manages feature requests, please consult the feature request management document. |
There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment. For more information on how the project manages feature requests, please consult the feature request management document. |
There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment. For more information on how the project manages feature requests, please consult the feature request management document. |
Is your feature request related to a problem? Please describe.
No. Improve the
fs
module, without the need to spawn child process for basic operations. (Like crate a named fifo pipe)Add to the
fs
module methods:fs.mkfifo
to create a fifo pipefs.mknod
for filesystem nodeThe text was updated successfully, but these errors were encountered: