Conversation
|
|
||
| "use strict"; | ||
| const colors = require("colors"); | ||
| const fsp = require("fs-extra"); |
There was a problem hiding this comment.
We can remove fs-extra from package.json now, right?
There was a problem hiding this comment.
copydeps still uses fs-extra for its own utility functions, but maybe we could cook our own ones.
There was a problem hiding this comment.
I checked. cp is being used only for files (not directories), so we can use the native one easily. And we have fs.rmdir and fs.unlink for fsp.remove 🎉
There was a problem hiding this comment.
@saschanaz Do you plan to fix above here or separate PR?
There was a problem hiding this comment.
Hmm, maybe a separate one.
|
Should we update this too? |
Ah yes... but should we defer this until version 8 loses its support? Not sure. |
|
|
|
The API is introduced in Node.js 10, but yes, it will break 8. |
marcoscaceres
left a comment
There was a problem hiding this comment.
This is in node lts, right?
Sure 😃 |
|
We should target active lts only. Ok to delete 8. |
|
One notable thing is that nodejs/node#26581 is not backported into 10 LTS yet, so using ReSpec there may emit some warnings. |
Like this... Looks like we should wait a bit more 😅 |
|
Lets pipe it through |
|
The warnings are ok IMO. Reading the history, the API did not change from when it was experimental to when it became stable... so technically, it was stable. Also, the warning don’t affect processing, so I think it’s fine to ship. |
Uses
fs.promiseswhich is now marked as stable.