Shutting the project down gracefully doesn't mean it has to end, and it doesn't mean failure: shutting down the project gives invested community members the chance to fork it and demonstrate that they want to put the work in to run a natural successor to your project, and people will naturally gravitate towards the best fork over time. Afterall, without people with a vision leading it, it's just code.
Handing over ownership feels cleanest but it's rarely the best outcome (unless you're handing it over to a natural successor).
Just wanted to say thank you for creating and support jsweet all these years :) I hope you find a good owner.
https://adoptoposs.org/ is the next best thing to announce and find more maintainers. The announcement blog post has a few more links that might be of interest to you: https://betterprogramming.pub/how-to-keep-open-source-softwa...
However, you have to be aware that the initial purpose of JSweet was not to port all Java libs to JS. JSweet allows the transpiler to be customized (with extensions) to map Java APIs to JS ones so that you don't necessarily need a JS runtime. It's all explained in the "Extending the transpiler" section of the core doc: https://github.com/cincheo/jsweet/blob/master/doc/jsweet-lan...
