Node.js Q&A
summary
Recommends turning off package lifecycle scripts when installing because both npm audit and yarn still run arbitrary install scripts; Snyk creates and offers git-diff patches for unpatched vulnerabilities and teams use patch-package as an alternative. Streams work well for JSON and large files; use createReadStream for images, worker threads plus message queues for horizontal stream processing, and async iterators (Node 10+) for generator-style pipelines. Kubernetes is favored for orchestration while Cloud Run/Heroku or FaaS are viable tradeoffs. Use query builders/ORMs to avoid SQL injection and name booleans with is/has.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:00Security
- 2:30Buffer types
- 3:50Kubernetes
- 4:55Cloud platforms
- 6:20Vulnerability detection
- 9:00Name conventions
- 10:40Mixing approaches
- 11:40Horizontal scaling
- 13:20Automated package patching
- 14:40Name things in Nodejs
- 18:10Share your questions
- 19:00How to use streams to read base64 images
- 20:30How can we learn to test and hack our own projects
- 23:30Whats better to use pure SQL or query builders
- 26:00What are the prerequisites
- 27:40Naming colors
- 30:35Outro
related talks
32mNODE.JS WORLD
47mNode.js Security: Breaking The Loop
02h 24mHow to Node.js - Part 2
30mNodeJS: Patterns and Tools to Ship to Production with Confidence
45mAsk the Maintainer: Nodejs
47mBlack Clouds and Silver Linings in Node.js Security
01h 02mDiscussion on Technologies: Node.js
33mStrategic Node.js crossroads in 2023