fedemengo/nodebestpractices

Issues

• 2.4 Handle errors centrally

  #10 opened 6 years ago by fedemengo
  0

• START HERE - Some information!

  #59 opened 6 years ago by fedemengo
  2

• 5.18. Don't route logs within the app

  #58 opened 6 years ago by fedemengo
  0

• 5.17. Use an LTS release of Node.js

  #57 opened 6 years ago by fedemengo
  0

• 5.16. Design automated, atomic and zero-downtime deployments

  #56 opened 6 years ago by fedemengo
  0

• 5.15. Set NODE_ENV=production

  #55 opened 6 years ago by fedemengo
  0

• 5.14. Assign a transaction id to each log statement

  #54 opened 6 years ago by fedemengo
  0

• 5.13. Use tools that automatically detect vulnerabilities

  #53 opened 6 years ago by fedemengo
  0

• 5.12. Be stateless, kill your servers almost every day

  #52 opened 6 years ago by fedemengo
  0

• 5.11. Get your frontend assets out of Node

  #51 opened 6 years ago by fedemengo
  0

• 5.10. Measure and guard the memory usage

  #50 opened 6 years ago by fedemengo
  0

• 5.9. Make your code production-ready

  #49 opened 6 years ago by fedemengo
  0

• 5.8. Discover errors and downtime using APM products

  #48 opened 6 years ago by fedemengo
  0

• 5.7. Create a ‘maintenance endpoint’

  #47 opened 6 years ago by fedemengo
  0

• 5.6. Utilize all CPU cores

  #46 opened 6 years ago by fedemengo
  0

• 5.5. Guard process uptime using the right tool

  #45 opened 6 years ago by fedemengo
  0

• 5.4. Lock dependencies

  #44 opened 6 years ago by fedemengo
  0

• 5.3. Delegate anything possible to a reverse proxy

  #43 opened 6 years ago by fedemengo
  0

• 5.2. Increase transparency using smart logging

  #42 opened 6 years ago by fedemengo
  0

• 5.1. Monitoring!

  #41 opened 6 years ago by fedemengo
  0

• 4.11 Carefully choose your CI platform

  #40 opened 6 years ago by fedemengo
  0

• 4.10 Refactor regularly using static analysis tools

  #39 opened 6 years ago by fedemengo
  0

• 4.9 Use docker-compose for e2e testing

  #38 opened 6 years ago by fedemengo
  0

• 4.8 Inspect for outdated packages

  #37 opened 6 years ago by fedemengo
  0

• 4.7 Check your test coverage

  #36 opened 6 years ago by fedemengo
  0

• 4.6 Tag your tests

  #35 opened 6 years ago by fedemengo
  0

• 4.5 Constantly inspect for vulnerable dependencies

  #34 opened 6 years ago by fedemengo
  0

• 4.4 Avoid global test fixtures and seeds, add data per-test

  #33 opened 6 years ago by fedemengo
  0

• 4.3 Detect code issues with a linter

  #32 opened 6 years ago by fedemengo
  0

• 4.2 Include 3 parts in each test name

  #31 opened 6 years ago by fedemengo
  0

• 4.1 At the very least, write API (component) testing

  #30 opened 6 years ago by fedemengo
  0

• 3.12 Use arrow function expressions

  #29 opened 6 years ago by fedemengo
  0

• 3.11 Use Async Await, avoid callbacks

  #28 opened 6 years ago by fedemengo
  0

• 3.10 Use the === operator

  #27 opened 6 years ago by fedemengo
  0

• 3.9 Require modules by folders

  #26 opened 6 years ago by fedemengo
  0

• 3.8 Require modules first

  #25 opened 6 years ago by fedemengo
  0

• 3.7 Prefer const over let. Ditch the var

  #24 opened 6 years ago by fedemengo
  0

• 3.6 Use naming conventions

  #23 opened 6 years ago by fedemengo
  0

• 3.5 Name your functions

  #22 opened 6 years ago by fedemengo
  0

• 3.4 Don't Forget the Semicolon

  #21 opened 6 years ago by fedemengo
  0

• 3.3 Start a Codeblock's Curly Braces on the Same Line

  #20 opened 6 years ago by fedemengo
  0

• 3.2 Node.js specific plugins

  #19 opened 6 years ago by fedemengo
  0

• 3.1 Use ESLint

  #18 opened 6 years ago by fedemengo
  0

• 2.11 Fail fast, validate arguments using a dedicated library

  #17 opened 6 years ago by fedemengo
  0

• 2.10 Catch unhandled promise rejections

  #16 opened 6 years ago by fedemengo
  0

• 2.9 Discover errors and downtime

  #15 opened 6 years ago by fedemengo
  0

• 2.8 Test error flows

  #14 opened 6 years ago by fedemengo
  0

• 2.7 Use a mature logger to increase error visibility

  #13 opened 6 years ago by fedemengo
  0

• 2.6 Exit the process gracefully

  #12 opened 6 years ago by fedemengo
  0

• 2.5 Document API errors

  #11 opened 6 years ago by fedemengo
  0