> For a proper way this would work, you the user would contribute your time for those features so you don't overburden the maintainer, but people like you won't and so this is where we're at.
Sure, if you're up front and honest from the beginning then some users will do that, the majority are likely to go for other offerings which don't suffer this problem. Vanishingly few users are going to be cool with features disappearing and then reappearing later on with a price tag attached, which is the scenario we're talking about.
In reality, 99.9% of the users are going to be using whatever free thing is available and your project will live for just about as long as you personally care about it. Rightly or wrongly, the maintainer's work/life balance isn't on the forefront of your mind when you're looking at npm packages, no amount of grandstanding will change that.