-
-
Notifications
You must be signed in to change notification settings - Fork 184
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
Not working with Node.js 14 #265
Labels
Comments
giggio
added a commit
that referenced
this issue
Apr 22, 2020
Only until #265 is fixed Also reformats the build file
Looks like this is already fixed on node master |
Node.js 14.1.0 fixed the issue. The build just finished with it, and it worked fine. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a problem upstream: max-mapper/extract-zip#94
I'm not sure if this is Node.js' problem or extract-zip's problem.
This is the log I get on my machine when I enable debug:
Node.js 14
And this is the log on Node 13:
Node.js 13
The difference is:
I also noticed that the file is actually extracted, but the script stops, I guess Node.js crashes.
This are the build logs:
https://dev.azure.com/giggio/node-chromedriver/_build/results?buildId=297&view=logs&j=edbbe288-f062-5a83-ca13-a390764a1b06&t=a97f51c5-49b6-5323-b0ad-80e976d7c9ec
I'm willing to give it some time so it can fix itself (Node or Extract-zip), but if anyone is willing to send a PR to patch it until then, I'll look into it.
The text was updated successfully, but these errors were encountered: