Skip to content
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

Why express and not Koa? #24

Open
espoal opened this issue Jul 2, 2017 · 2 comments
Open

Why express and not Koa? #24

espoal opened this issue Jul 2, 2017 · 2 comments

Comments

@espoal
Copy link

espoal commented Jul 2, 2017

Why express and not Koa, or Micro?

I vote koa because it uses promises, enabling deferred startup, e.g.: the server starts immediately, and eventually it will connect to the db.

@Sly777
Copy link
Owner

Sly777 commented Jul 2, 2017

Hey @servermeta, Actually I used "express.js" because It's well-maintained and stable framework on "node.js". And also It's default one on "next.js" :) But the thing is that maybe we can create add-on system that developers can choose any framework that they want.

for example;
Developer runs npm run add-ons
-> Choose add-on section
---> 1) Server frameworks <=
---> 2) Marketing
---> Exit

-> Which "Server framework" do you want to use?
---> 1) Express <=
---> 2) Koa
---> 3) Hapi
---> 4) Micro

-> It will overwrite your server.js file. Do you want to continue?
---> Yes <=
---> No

And then It will replace with new framework after install packages, replace server.js.

@srghma
Copy link
Contributor

srghma commented Aug 10, 2017

Why even bother yourself with different servers if its intent is only to render page, if you want api - make separate project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants