[Idea]: achieve feature parity with builtin Node.js fs module

[kgryte]

Idea

Achieve feature parity with Node.js fs package. We currently only support a limited selection of fs methods. Would be useful to support more.

Part of this work involves providing an abstraction layer of Node.js built-ins in order to support newer functionality (e.g., options and/or behavior) not present in older Node.js versions. This is similar in concept to the userland readable-stream package.

Expected Outcomes

stdlib will have complete feature parity with Node.js built-ins.

Involved Software

No other software is necessary.

Prerequisite Knowledge

JavaScript, Node.js.

Difficulty

Intermediate. Could require some creative solutions to ensure that abstractions work for older Node.js versions.

Project Length

175/350 hours. Can be scoped accordingly.

Potential Mentors

@kgryte @Planeshifter @steff456

[kgryte]

For those interested in working on this idea, you are advised to do a fair amount of R&D to determine the backward compatibility story. For newer Node.js fs features, such as recursively making directories, polyfilled workarounds are not always straightforward. Hence, you should spend a fair amount of time reading through the Node.js documentation, reading version logs, see which features have been added when, and then determining how you will provide fallbacks such that behavior is consistent across all supported Node.js versions.

[kgryte]

Please do not simply submit a proposal saying "I will do APIs A, B, C this week, then D, E, F the following week, and so on and so forth", without having a thorough and well-considered approach for backward compatibility.