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

Add support to node 16. #200

Closed
mshima opened this issue Apr 28, 2021 · 7 comments
Closed

Add support to node 16. #200

mshima opened this issue Apr 28, 2021 · 7 comments

Comments

@mshima
Copy link

mshima commented Apr 28, 2021

Current version fails with node 16.

It should support node >= instead of a particular version.

See yeoman/yo#662

@scalvert
Copy link

Potential fix: #201

@christianpaquin
Copy link

Is there an ETA for node 16 support?

@balupton
Copy link
Member

balupton commented May 31, 2021

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.

https://bevry.me/fund

@balupton
Copy link
Member

Support is coming this week. Work has already commenced.

I'm streaming the process on Twitch:
https://twitch.tv/balupton

Please consider funding, as I'm a bootstrapped soloprenuer whose only salary is donations, hence delays.
https://bevry.me/fund

@balupton
Copy link
Member

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.

@balupton
Copy link
Member

balupton commented Jul 28, 2021

Bug was over in Editions:

bevry/editions#235

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.


❤️ Please consider funding my work so things like this never happen in the first place, or when they do happen, I can afford the time to fix them speedily. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants