Node.JS Practices

@nodepractices

Cherry picked and non-trivial Node.JS best practices. Collected and curated bi-weekly from all social platforms

Joined June 2016
25 Photos and videos Photos and videos

Tweets

You blocked @nodepractices

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @nodepractices

  1. Jun 7

    Best Practice: kill your servers every day. Have you ever heard about the Phoenix bird?

    5 likes
  2. Mar 16

    Best Practice: Always guard and restart your processes. Be sure to choose the right tool for the mission

    3 retweets 2 likes
  3. Retweeted
    15 Dec 2016

    Best Practice: Assign transaction-id to each log statement - get the full picture when inspecting an error

    5 retweets 2 likes
  4. Retweeted
    1 Dec 2016

    Best Practice: Have an automatic eye on vulnerabilities using tools like nsp and snyk

    3 retweets 5 likes
  5. 15 Dec 2016

    Best Practice: Assign transaction-id to each log statement - get the full picture when inspecting an error

    5 retweets 2 likes
  6. 1 Dec 2016

    Best Practice: Have an automatic eye on vulnerabilities using tools like nsp and snyk

    3 retweets 5 likes
  7. Retweeted
    26 Oct 2016

    Best Practice: Set Node_ENV=production otherwise it might make slower in a factor of three!

    16 retweets 34 likes
  8. 17 Nov 2016

    Best Practice: easily discover synchronous code blocks using --trace-sync-io

    1 retweet 3 likes
  9. Retweeted
    3 Nov 2016

    Best Practices Special Edition: 66 slides that summarize the best articles and practices on error handling

    1 retweet 1 like
  10. Retweeted
    6 Oct 2016

    Best Practice: Store configuration data in environment variables, config files are not friendly

    1 retweet 1 like
  11. 3 Nov 2016

    Best Practices Special Edition: 66 slides that summarize the best articles and practices on error handling

    1 retweet 1 like
  12. Retweeted
    15 Aug 2016

    Best Practice: Do Require(‘folder’) but not files directly

    3 retweets 2 likes
  13. Retweeted
    22 Sep 2016

    Best Practice: Prevent straightforward security attacks using 'Helmet', one-minute setup

    2 retweets 3 likes
  14. 26 Oct 2016

    Best Practice: Set Node_ENV=production otherwise it might make slower in a factor of three!

    16 retweets 34 likes
  15. 6 Oct 2016

    Best Practice: Store configuration data in environment variables, config files are not friendly

    1 retweet 1 like
  16. Retweeted
    14 Sep 2016

    Best Practice: Increase modularity by defining routes within components, not in app.js

    3 retweets 3 likes
  17. 22 Sep 2016

    Best Practice: Prevent straightforward security attacks using 'Helmet', one-minute setup

    2 retweets 3 likes
  18. Retweeted
    28 Jul 2016

    Best Practice: Use NPM config file (.npmrc) to prevent dependencies drifting

    3 retweets 1 like
  19. 19 Sep 2016

    Best Practice: Distinguish operational vs programmer errors to prevent...

    3 retweets 5 likes
  20. 15 Sep 2016

    Dedicating the next two days to best practices from : don't forget to handle unhandled promise...

    1 like

@nodepractices hasn't Tweeted yet.

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·