0:00 - express v5 Released 0:25 - express v5 docs still in beta 0:49 - express v5 changelog / migrating guide 0:56 - rejected promised automatically handled 1:05 - setting up local example api 1:35 - api code tour 1:51 - add broken router 2:34 - throw error in handler without try / catch 3:19 - express error handler setup 4:00 - throw error in handler in async handler without try / catch 5:05 - Installing v5 5:16 - express types not updated yet 5:41 - sendfile removed / renamed to sendFile 5:56 - using express v5 6:31 - send method status argument removed 7:03 - path route matching syntax change 7:16 - req.query not writable 7:20 - async handlers are now caught 7:57 - deprecated methods from v4 are removed in v5 9:01 - pluralized accepts method names 9:09 - app.param leading colon ignored 9:14 - res.send no long accepts just status code - use res.sendStatus 9:47 - v5 upgrades not that bad 9:59 - v5 type updates waiting to be merged 10:21 - Thanks!
Brother, I had a Node.js project, then we changed the method of connecting to SQL, and all the SQL queries slowed down. Later, we reverted to the old method, but it couldn't reach the old speed again. What can be done? Windows Server Data Base Mssql
Feels like the evolution of js libraries has been promise friendly > typesafe > web standards. This lets me remove a dependency on promiserouter or whatever it’s called but man…it’s years late lol
Not to sound ungrateful, but I'm surprised Express still doesn't have first-class support for HTTP/2. My company will probably have to migrate to Fastify because of this.
For me this is a bummer „Express 5 no longer supports the signature res.json(obj, status). Instead, set the status and then chain it to the res.json() method like this: res.status(status).json(obj).“ .. because now we need to always send a status?! Why can’t we keep default 200?
I think if you want to use the default 200 status code, just use the res.json() or res.send() without setting the status argument. There is no need to use res.status(200) manually and chain it into them. Seems like you only need res.status() when you want to send status code other than 200. CMIIW
@@dimasadnan4873 mhhh … to me the E5 note reads like as if they removed res.json() and replaced it with res.status().json() and as a consequence res.json().status() is not possible
See all my settings here: github.com/CodingGarden/vscode-settings I go over everything in this video on Syntax: th-cam.com/video/85q9FTdVyJs/w-d-xo.html
![[LIVE] : ONE ลุมพินี 86 | คู่เอก "คมเพชร vs ชาติพยัคฆ์"](http://i.ytimg.com/vi/m3q_dRYDuU8/mqdefault.jpg)
0:00 - express v5 Released
0:25 - express v5 docs still in beta
0:49 - express v5 changelog / migrating guide
0:56 - rejected promised automatically handled
1:05 - setting up local example api
1:35 - api code tour
1:51 - add broken router
2:34 - throw error in handler without try / catch
3:19 - express error handler setup
4:00 - throw error in handler in async handler without try / catch
5:05 - Installing v5
5:16 - express types not updated yet
5:41 - sendfile removed / renamed to sendFile
5:56 - using express v5
6:31 - send method status argument removed
7:03 - path route matching syntax change
7:16 - req.query not writable
7:20 - async handlers are now caught
7:57 - deprecated methods from v4 are removed in v5
9:01 - pluralized accepts method names
9:09 - app.param leading colon ignored
9:14 - res.send no long accepts just status code - use res.sendStatus
9:47 - v5 upgrades not that bad
9:59 - v5 type updates waiting to be merged
10:21 - Thanks!
Brother, I had a Node.js project, then we changed the method of connecting to SQL, and all the SQL queries slowed down. Later, we reverted to the old method, but it couldn't reach the old speed again. What can be done? Windows Server Data Base Mssql
Absolutely respect the library, the author, and the people that made the effort to actually ship this. But. I'm not coming back after using Hono.
@@mikevaleriano9557 yes!
After 10 years, another version update. The stability of this is outstanding.
Love to see a Express.js vs Hono.js comparison
youre the best, cj! love from brazil
10 min video I love it
Feels like the evolution of js libraries has been promise friendly > typesafe > web standards. This lets me remove a dependency on promiserouter or whatever it’s called but man…it’s years late lol
Thanks CJ
Not to sound ungrateful, but I'm surprised Express still doesn't have first-class support for HTTP/2. My company will probably have to migrate to Fastify because of this.
I moved to Hono
wow been a minute CJ
For me this is a bummer „Express 5 no longer supports the signature res.json(obj, status). Instead, set the status and then chain it to the res.json() method like this: res.status(status).json(obj).“ .. because now we need to always send a status?! Why can’t we keep default 200?
I think if you want to use the default 200 status code, just use the res.json() or res.send() without setting the status argument. There is no need to use res.status(200) manually and chain it into them. Seems like you only need res.status() when you want to send status code other than 200. CMIIW
@@dimasadnan4873 mhhh … to me the E5 note reads like as if they removed res.json() and replaced it with res.status().json() and as a consequence res.json().status() is not possible
Did CJ accidentally upload this to the wrong channel?
No this was from a Coding Garden live stream 😄
pls vscode theme :) ?
See all my settings here: github.com/CodingGarden/vscode-settings
I go over everything in this video on Syntax: th-cam.com/video/85q9FTdVyJs/w-d-xo.html
Express is a decade late 😂
but still used by most of the node community! so its a win in their book
@@statuschannel8572 they already lost
Late to what? Nothing has really changed since then.
Hello twitch 😂😂