"Be not afraid!"

In the era of async/await, the grass has never been greener over here in Node.js-land. But there are still a few major gotchas you need to watch out for, and some of them are less than obvious. Mike will review the most common practical risks and mistakes our team sees in real-world Node.js applications. And then he'll explain why it's actually fine... why, despite all that, Node.js is even more of an awesome choice for your application in 2019.

Mike McNeil (@mikermcneil) has been an avid business user and evangelist for Node.js for the last seven years. He's also the creator of Sails.js, a popular open-source MVC framework that's kind of like Rails for Node.js.

Transcript

1. Austin Node.js meetup November 2018 @
2. Thank you!
3. The Company Mike McNeil @mikermcneil founder & CEO of sails co. digital studio (a.k.a. design/dev/product shop) open-source MVC framework for Node.js creator of
4. "Be not afraid!" @mikermcneil
5. What's wrong with Node.js?
6. What's wrong with some Node.js apps?
7. 1. Not using await
8. 1(A). Throwing in callbacks
9. 1(B). Ignoring errors in callbacks or in promise chains
10. 1(C). Not using await... on purpose (drinking performance kool-aid)
11. 1(D). Not using await... on accident
12. 2. Not handling 'error' events
13. 3. Lack of structure
14. 3(A). Named functions being declared all over the place
15. (in our server-side Node.js code, if we give a function a name, then we also give it its own file)
16. 3(B). Not having a way of figuring out all the places where a given function is being called from
17. (can you grep for it?)
18. 3(C). Insufficient abstraction
19. (express is a fantastic "build your own framework" framework)
20. 4. Fetching WAAAAYYY too many things at the same time
21. 5. Fetching a normal amount of things…but WAAAYYYY too many times
22. @mikermcneil Questions?