You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I completely agree with the promises over callbacks approach this lib is taking, However, the current FS Node API is still callback based with an experimental promises API. This makes it difficult to work with 3rd party libraries, like Webpack.
I wonder what you think about being closer to the spec and offering a callback version of the FS. Even with a subset of the node FS, just returning the callbacks would make this work.
There is no need to add overhead to the existing FS implementation. Just a compatible implementation to the node spec; adding the experimental .promises API would make it perfect 😉
FYI - from what I saw Webpack uses the current node FS API for readFile, writeFile, stat, rmdir, unlink, purge (optional), readlink (when resolve.symlinks is not turned off) while also requiring mkdirp and join directly on the FS API for some reason (webpack-dev-middleware even validates it)
The text was updated successfully, but these errors were encountered:
- Drop node 8 support.
- Exposes all promise-based API under `promises` field (matches Node 10+).
- Node package uses Node 10's native `promises` API instead of promisifying them every time via `proper-fs`.
- Callback-style API is now exposed as well from async file systems.
- `readlink` (promise and callback style) and `readlinkSync` is now exposed as well, for better compatibility with libraries expecting Node-style API.
closes#14
- Drop node 8 support.
- Exposes all promise-based API under `promises` field (matches Node 10+).
- Node package uses Node 10's native `promises` API instead of promisifying them every time via `proper-fs`.
- Callback-style API is now exposed as well from async file systems.
- `readlink` (promise and callback style) and `readlinkSync` is now exposed as well, for better compatibility with libraries expecting Node-style API.
closeswixplosives#14
I completely agree with the promises over callbacks approach this lib is taking, However, the current FS Node API is still callback based with an experimental promises API. This makes it difficult to work with 3rd party libraries, like Webpack.
I wonder what you think about being closer to the spec and offering a callback version of the FS. Even with a subset of the node FS, just returning the callbacks would make this work.
There is no need to add overhead to the existing FS implementation. Just a compatible implementation to the node spec; adding the experimental
.promises
API would make it perfect 😉FYI - from what I saw Webpack uses the current node FS API for
readFile
,writeFile
,stat
,rmdir
,unlink
,purge
(optional),readlink
(whenresolve.symlinks
is not turned off) while also requiringmkdirp
andjoin
directly on the FS API for some reason (webpack-dev-middleware even validates it)The text was updated successfully, but these errors were encountered: