Start learning with our library of video tutorials taught by experts. Get started
Viewed by members. in countries. members currently watching.
This could be a good message, could be a bad message, could be informative. We can make that behavior more apparent if we know there's an error, or we know it's informational, by changing the word log to one of four other words. We could change log to debug. Now I will just comment out the other lines right now. Clear the console on the left and run it. Not much of a difference on that one. Change debug to info. Now I get the little I icon here.
Change info to warn. Now I get the yellow and the exclamations mark. Or change console to error and run that, and we actually get the error message here. It's the same message, but different icons for them. Though note, if you do have an error, you will also now get it in the status bar as well, but for the most part we will just be doing console.log, the most straightforward way of doing this. We can do a few other things with the console, as we'll see later, like measuring performance and how long a script is taking to run, but if nothing else, console.log is going to come in immensely useful for us to understand our own code better.
Access exercise files from a button right under the course name.
Search within course videos and transcripts, and jump right to the results.
Remove icons showing you already watched videos if you want to start over.
Make the video wide, narrow, full-screen, or pop the player out of the page into its own window.
Click on text in the transcript to jump to that spot in the video. As the video plays, the relevant spot in the transcript will be highlighted.