should I use express for future projects?

express was the most promising web server for node.js, it seems the development has been slowing down considerably for the last few years, as of today ES6 is not added, no async/await work in sight either, this is quite a surprise considering the (still) fast advancements on frontend frameworks, node.js and javascript. What is going on?

Maybe it’s time for a fundraise to re-ignite the development for this great project? or is there something else replacing it so nobody cares that much? or node.js framework is losing its popularity in general after some over-hyper?

Really want to see a django alike framework in node.js.

Author: Fantashit

4 thoughts on “should I use express for future projects?

  1. I’ll prefix my response with: ultimately, the decision is up to you; I’m not really going to try and beg for you use to Express 🙂

    As far as the comments, there is a lot to distill, and without you providing examples, it is really hard to know if what you’re asking for is (a) already available for preview in the latest Express 5 alpha (b) is not available but on our roadmap or (c) has never been brought up until just now.

    If you’re willing to, it would be awesome if you could expand on each of the items you’re looking for to exist, articulate exactly what you mean by them and what it would look like for it to exist in the framework, so we can get a common understanding of what, for example “as of today ES6 is not added” even means. The version of ES you use in your code is unrelated to the underlying library at a generic level, so getting specifics here on what this means would help us provide a better answer.

  2. Hi @Bharatbisht thanks for bring this up. Every day I write my Express apps in ES6+, so not really sure what exactly you’re referring to when you say “[…] can we see the support of es6 in express”. Without you providing examples, it is really hard to know if what you’re asking for is (a) already available for preview in the latest Express 5 alpha (b) is not available but on our roadmap or (c) has never been brought up until just now.

    If you’re willing to, it would be awesome if you could expand on your statement, articulate exactly what you mean and what it would look like for it to exist in the framework, so we can get a common understanding of what, for example “the support of es6 in express” even means. The version of ES you use in your code is unrelated to the underlying library at a generic level, so getting specifics here on what this means would help us provide a better answer.

  3. I am active in Express every day, for example you got an immediate response to your question. Is that not active? What would make it “active” ? For example you say you how it becomes more active. I would like to agree, though I feel as if it is, so perhaps our definition of active just differs. If you can lay out your definitions of what it would mean to be active, that would help determine what would need to change, if anything, to meet your expectations.

    Thank you for your answer.
    I want express to have a roadmap and a quick iteration of iterations.
    I noticed that 5.0 has not released the official version for 2 years.

Comments are closed.