-
Notifications
You must be signed in to change notification settings - Fork 64
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
Fix usage of jbrowse-cli on node 10.9 related to fs.promises #1461
Conversation
Note that 10.9 also prints out the warning "(node:109940) ExperimentalWarning: The fs.promises API is experimental" so this is early days of node. Also, can't replace del with fs.rmdir with recursive:true option because that was added in like 10.12 to sidestep the del failing |
Codecov Report
@@ Coverage Diff @@
## master #1461 +/- ##
==========================================
+ Coverage 59.76% 59.80% +0.04%
==========================================
Files 426 426
Lines 19086 19093 +7
Branches 4371 4371
==========================================
+ Hits 11406 11418 +12
+ Misses 7386 7381 -5
Partials 294 294
Continue to review full report at Codecov.
|
Note also that using nvm install 10.0 This does not work and produces an lstat error
|
So this basically adds a little more node 10 compatibility at the price of a little weirdness (I am not even sure why this alternative import style works in this case) |
Interesting. It would be good if we could enforce this with a lint rule or something, but I'm not sure if there's an easy way to do that. |
do the TS compiler params for the CLI perhaps need to be tweaked? maybe they are targeting a more recent node version, and that's why the previous import statements don't work? |
To me, this problem is indicative of some wild stuff that is slightly before fs.promises got standardized This means we could a) Take this PR as is, establish 10.9 or something like that as a minimum, and disallow 10.0 |
well it's a net improvement, so merged |
Fixes #1440
This is kind of a weird one but
This fails with the lstat error described in #1440
With this PR though it is fixed
Note that
yarn test products/jbrowse-cli
does not pass with node 10.9 still due to something weird about testUtil, full errorThat goes back to something in the del command/package I think