You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered: