-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add support to node 16. #200
Comments
Potential fix: #201 |
Is there an ETA for node 16 support? |
End of June is the target. I have a bunch of changes in bevry/boundation that need to be released first, which is our automated maintenance tool, and the next two weeks are non-software projects. Please consider posting a bounty or funding my work, as it is all done for free in my spare time as a solo indie dev with zero support nor salary. |
Support is coming this week. Work has already commenced. I'm streaming the process on Twitch: Please consider funding, as I'm a bootstrapped soloprenuer whose only salary is donations, hence delays. |
Support is still on the way and is still the active task (just had more sub tasks than expected). Links from prior post are still relevant, that is progress can be followed on Twitch and funded so that I get a return on this time investment. |
Bug was over in Editions: A forced editions dependency upgrade is happening on all the Bevry packages now via boundation. Once the automated release happens in the coming hours, it should resolve this problem. |
Current version fails with node 16.
It should support node >= instead of a particular version.
See yeoman/yo#662
The text was updated successfully, but these errors were encountered: