nodenv is an rbenv fork for node that has an active group of maintainers (disclaimer: I am one of said maintainers) and is in the process of migrating to the nodenv github org. We also perform regular merges down from rbenv upstream, to stay abreast of the latest rbenv bug fixes and features.
I see that nenv is also an rbenv fork. Are there features that have been added to nenv that are lacking in rbenv from which nodenv could benefit? Are you interested in joining forces and adding any nenv features to nodenv (and perhaps sunsetting nenv in favor of nodenv)?
(I realize that opening an issue against a project and suggesting that said project be sunset is rather brash. But I mean no offense and only suggest this so as to unify the rbenv-for-node community. Indeed, this has already taken place one with the merging/deprecating of wfarr's nodenv into/in favor of oinutter's nodenv.)
nodenv is an rbenv fork for node that has an active group of maintainers (disclaimer: I am one of said maintainers) and is in the process of migrating to the nodenv github org. We also perform regular merges down from rbenv upstream, to stay abreast of the latest rbenv bug fixes and features.
I see that nenv is also an rbenv fork. Are there features that have been added to nenv that are lacking in rbenv from which nodenv could benefit? Are you interested in joining forces and adding any nenv features to nodenv (and perhaps sunsetting nenv in favor of nodenv)?
(I realize that opening an issue against a project and suggesting that said project be sunset is rather brash. But I mean no offense and only suggest this so as to unify the rbenv-for-node community. Indeed, this has already taken place one with the merging/deprecating of wfarr's nodenv into/in favor of oinutter's nodenv.)