-
Notifications
You must be signed in to change notification settings - Fork 206
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
Is EvaporateJS Still Being Developed #450
Comments
Hi @TheWiseNoob, I am the one who should respond here probably, although I am not officially an active developer here, and I don't have access to the settings of this repo, to NPM or Travis. That would be up to @tomsaffell, who is not responding for years. EvaporateJS is not being actively developed, however, we are trying to maintain it here as much as we can. I am totally willing to help with development here, we need some quality contributors that would be able to help as well. There are some valid PRs open that need looking after, we should move evaporate to a separate namespace, set up new NPM and Travis, and we can start planning things that are needed to be done (like serious refactoring of the tooling and methods, security optimizations, some long-open issues, proper CI, etc.). |
I'm also willing to maintain this project. Perhaps it's time to migrate it to EvaporateJS/EvaporateJS? |
Was anybody able to continue maintaining this? Is the 3rd version using TypeScript and Webpack still being developed? |
Thanks for reaching out, the TS needs to be tested, merged and we can start doing releases. Any help with picking up PRs, testing, or anything really is welcome. |
Is there still someone willing to help with the v3 TS push? @TheWiseNoob @psdon @mattmoreira? |
The last commit was in September of last year. Is there some other place to learn the development status of EvaporateJS? Is it still being developed?
The text was updated successfully, but these errors were encountered: