I’ll try to share a summary of the things we covered each week.
Here you can find the previous post in the series.
This week we demonstrated couple of subjects:
We showed several usage examples based on the official documentations and this talk —
Most talk was based on examples from the MDN page on the subject.
Debugging Node.js with Chrome DevTools
Chrome released an update to ‘chrome://inspect’ page — you can now open dedicated devtools window which automatically attach to node when running with the ‘inspect’ flag.
You can also choose from a list of running node instances.
This post by Paul Irish has been updated to contain this change.
Support for Node.js debuggability landed in Node.js master in May 2016. You can see it in action in the DevTools 2016…medium.com
The story of how I got tired of the default developer tools and made a better responsive design tool in 10 hours.medium.com
ES modules are landing in browsers! Here are the HTML-specific differences you need to be aware of.jakearchibald.com
TL;DR: see https://en.wikipedia.org/wiki/Betteridge%27s_law_of_headlines. Or just skip to the summary at the end of the…hackernoon.com