Skip to content
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

chore: run unit tests on node 10.15 + fix fs.promises access #6550

Merged
merged 2 commits into from Oct 26, 2020

Conversation

jackfranklin
Copy link
Collaborator

@jackfranklin jackfranklin commented Oct 26, 2020

We saw in #6548 that the
fs.promises module was experimental in Node <10.17 and as such we
introduced issues for users on 10.15.

Until we can drop Node v10 (it's EOL is 30-04-20201
https://github.com/nodejs/Release#release-schedule) we should run our
tests on an old Node 10 to avoid regressing in this area.

Closes #6548 .

We saw in #6548 that the
`fs.promises` module was experimental in Node <10.17 and as such we
introduced issues for users on 10.15.

Until we can drop Node v10 (it's EOL is 30-04-20201
https://github.com/nodejs/Release#release-schedule) we should run our
tests on an old Node 10 to avoid regressing in this area.
@jackfranklin
Copy link
Collaborator Author

Note that I'm expecting the 10.15 CI run to fail, but hoping that I can then patch #6549 in and that will fix it.

@jackfranklin
Copy link
Collaborator Author

@mathiasbynens PTAL at the latest commit. I took the work in #6549 but extracted it into a helper function that we can use in the mean time. That, plus running tests on Node 10.15, should ensure we don't hit this again.

@jackfranklin jackfranklin changed the title chore: run unit tests on node 10.15 chore: run unit tests on node 10.15 + fix fs.promises access Oct 26, 2020
src/common/helper.ts Outdated Show resolved Hide resolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Compatible issue with node@10.13 - node@10.17
2 participants