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
Question: The future of the Express development #5420
Comments
Hello, it is still being maintained. Express has many modules, which of course have lots of work that change outside. |
There are several issues about this currently open, so we don't need yet another one, and I will expand more when I get out if work tonight. |
Also, I am hoping that my prompt response demonstrates that I am closely watching and responding to everything and working as hard as a single person possibly can across the dozens of modules and still have a job and life :) |
Not that I could possibly help you (sadly still lack of knowledge), but how would you say could people help you the most right now with the development, if someone decides to start contributing now? Are there specific things with higher priority that needs to be adressed? |
Ya, there are lots of issues open that needs either triaging, replies to issues and more. I will try to get together some specifics when I get off work tonight for you. |
Hello,
I have noticed that the development activity of Express itself (not the middleware) has been declining.
The last stable release 4.18.2 is from Oct 8, 2022.
The last beta relelease 5.0.0-beta.1 is from Feb 16, 2022.
I also noticed, that Express' development in 2022 has been done by primarily one person (@dougwilson).
I would like to ask what the current situation of the Express development is.
Currently, Express is stable, and pretty popular according to npm download stats, but it wont stay stable in the future if maintenance is halted or abandoned.
Thats why I am wondering how the future of Express looks like. Mabye someone can give some clarification on that.
Thank you! :)
The text was updated successfully, but these errors were encountered: