I wonder if some of you veterans can give some advice to some of us, noob.
Are there any benefits to writing Node Vanilla using Express? More specifically, any particular scenario where using Express will not be an option? And finally, for tasks you can use for Express, how deep should you go within the layers of abstraction to find out what is going on?
I mean, there are many people who can create reliable and powerful web applications, and they donβt have a clue what Express really does for them.
Very much appreciated
, .
, Express - -. Node.
, , :
- - . raw Node, , .
, , , , ( ).
, . , , , " ". , , .
, , , vanilla node . 8000 , , . , , , :
, . , , , . , Walmart Hapi, , " ". , , - , . - , - socketcluster.io, -. .
Node, node. , . , npm - , node , , . , Node.js, .
Source: https://habr.com/ru/post/1667466/More articles:PostgreSQL PGDATA from host in Docker-System - dockerCompiling .Net Core VS17 - c #error in unit test vue.js karma: undefined is not a constructor () - javascriptUsing date and time to determine a high frequency event over a period of time - pythonFilter object object in javascript (filter or reduce?) - javascriptDifferent csrf token value in response header and browser cookies. Csrf error in django 1.9 - djangoNo connection can be made because the target machine actively refused it 127.0.0.1:32450 - c #AWS gets instance name in Java - javaFiles.write (): adding new lines to a text file - javaHow to replace keywords marked with {key} inside strings with value in dict ["key"] - pythonAll Articles