What is the problem this feature will solve?
Currently, creating Single Executable Applications in Node.js requires complex workarounds and monkey-patching of the fs module to access embedded resources. This approach:
- Makes Node.js harder to maintain due to ecosystem modules that monkey-patch core behavior[1]
- Creates compatibility issues when Node.js APIs change
- Lacks a standardized, official way to handle virtual file systems
- Forces developers to implement fragile solutions that may break with future Node.js updates
What is the feature you are proposing to solve the problem?
Implementing a VFS hooks API in Node.js core that would allow userland code to override read-only filesystem operations through a virtual file system, specifically to support Single Executable Applications (SEAs) as described in the FS hooks proposal.
What alternatives have you considered?
- Monkey-patching fs module: Current approach but problematic for maintainability
- Using Loaders API for fs replacement: Could work but not designed for this purpose
- External VFS libraries: Require significant setup and don't integrate cleanly with Node.js internals
What is the problem this feature will solve?
Currently, creating Single Executable Applications in Node.js requires complex workarounds and monkey-patching of the
fsmodule to access embedded resources. This approach:What is the feature you are proposing to solve the problem?
Implementing a VFS hooks API in Node.js core that would allow userland code to override read-only filesystem operations through a virtual file system, specifically to support Single Executable Applications (SEAs) as described in the FS hooks proposal.
What alternatives have you considered?