Last 12 weeks · 0 commits
0 of 6 standards met
Minor nitpick but I noticed in your event handlers you tend to use rather than , where the latter would greatly improve code clarity, modularity and DRYness since will always refer to the element that dispatched the event, a.k.a the element the user interacted with, whereas refers to the element the handler was attached to. So if you have an element that has several children expected to have the same functionality, you can simply append the event handler for that functionality to the parent and you would have fewer event listeners, which generally means less memory usage, no?
Repository: wesbos/Wes-Bos-Video-Notes. Description: These are notes that supplement the videos on Wes Bos Courses Stars: 81, Forks: 309. Primary language: JavaScript. Languages: JavaScript (100%). Open PRs: 9, open issues: 3. Last activity: 2y ago. Community health: 14%. Top contributors: wesbos, bcha92, easpaas, jbasoo, paidhi, paulschreiber, coreycougle, failedorbit, fdeters.
Using a later version of node and dependencies requires some modification to course code to continue to work as expected. In this case, the promisify import and function definition doesn't work as outlined in the video, and an updated method using node's built-in util module works well instead.