-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Node.js 10 #551
Comments
Got it! |
According to https://github.com/nodejs/Release; Node 10 is slated for release in April, which is also the time for the EOL of Node 4 LTS. I'm thinking we should probably cut one major release containing 10 support and dropping 4 support. |
Now, the question on our end is this: do we have to also support
@jprichardson @manidlou @JPeer264 Thoughts? |
I would argue yes, as this library should be a drop-in replacement for Also in the readme we kinda promise: |
@JPeer264 Understood; the counterpoint is that we already have promise support, so you'll never need to use |
Hm that's true. After lot of thinking now I think it might be better to keep it as is, but we should mention somewhere that |
yeah.. no need to add it! |
I have gotten clarity from the Node.js core team, and unflagged ESM (ES6 modules) support will not be landing in Node 10.0.0, though there's a possibility it'll land later on the 10.x line. So we don't need to worry about that for now. |
When using fs-extra on Node.js 10.1.0, an ExperimentalWarning is printed to console - see #577 |
Closing since this is no longer needed. |
Node.js 10 isn't out yet, but I just wanted to post this here so we're aware: https://twitter.com/jasnell/status/960733696461438976
It seems that
fs.promise.readFile()
etc. will have native promise support. I don't see a lot needing changed on our end, other than exposing this API when it's available.Can close this when all the maintainers have seen this.
The text was updated successfully, but these errors were encountered: