-
-
Notifications
You must be signed in to change notification settings - Fork 536
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 engine V8 compatibility is broken #940
Labels
Comments
This was referenced Jan 12, 2020
I'm going to try wrapping the old version of yn in a wrapper that converts null return values to undefined. That should achieve the desired behavior without upgrading yn, which avoids the problematic engine requirement. |
We can also add a |
This was referenced Jan 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ts-node is no longer work on Node V8, because yn is enforcing Node V10 compatibility.
Caused by: yn#26
The motivation for changing the V8 requirement to V10 is because Node.js V8 is no longer supported. I believe node engine requirement should indicate the engine(s) the module works with.
The text was updated successfully, but these errors were encountered: