Essential CSS
JavaScript Roadmap
Learn JavaScript
Mastering Web Typography
Practical Astro
Understanding Async JS
Unorthodox Tailwind
API Masterclass
Build and Deploy
The Beginner Freelancer
Real World Node
Profile Billing Logout
Learn JavaScript
Lesson Plan
  1. JavaScript and its ecosystem
    1. Welcome to Learn JavaScript!
    2. What is JavaScript used for?
    3. The JavaScript ecosystem
    4. Varying versions of JavaScript
  2. JS Basics
    1. Linking your JavaScript file
    2. Preparing your text editor
    3. The Console
    4. Comments
    5. On semicolons
    6. Strings, numbers and booleans
    7. Understanding Variables
    8. Understanding Functions
    9. The Flow of a Function
    10. Arrow functions
    11. Intro to objects
    12. If/else statements
    13. Comparing Objects
    14. The NOT operator
    15. Null and Undefined
    16. The BOM and the DOM
    17. Selecting an Element
    18. Changing Classes
    19. Listening to events
    20. Callbacks
  3. Building simple components
    1. How to think like a developer
    2. Starter files and Source codes
    3. Do this for every component
    4. đź›  Off-canvas menu: Building an off-canvas menu
    5. đź›  Modal: Building a Modal
    6. Lessons from the building process
    7. Debugging errors
    8. How to use a linter
  4. Arrays and loops
    1. Introduction to Arrays
    2. Array methods
    3. For loops
    4. The forEach loop
    5. Selecting multiple elements
    6. Nodes vs Elements
    7. đź›  Accordion: Building an accordion
  5. Dom basics
    1. Id, classes, attributes, and tags
    2. Changing CSS with JavaScript
    3. Getting CSS with JavaScript
    4. Changing Attributes
    5. Finding an element's size and position
    6. DOM Traversals
    7. đź›  Tabby: Building Tabby (A Tabbed component)
    8. đź›  Carousel: HTML and CSS
    9. đź›  Carousel: Switching slides with JavaScript
    10. đź›  Carousel: Working the dots
    11. đź›  Carousel: Positioning slides with JavaScript
  6. Events deep dive
    1. The listening element
    2. Default Behaviors
    3. Event propagation
    4. Event delegation
    5. Removing Event Listeners
    6. đź›  Modal: Closing the modal
    7. đź›  Accordion: Event delegation
    8. đź›  Tabby: Event delegation
    9. đź›  Carousel: Event delegation
  7. Transitions and Animations
    1. CSS Transitions
    2. CSS Animations
    3. Silky-smooth animations
    4. Integrating CSS transitions and animations with JavaScript
    5. Animating with JavaScript
    6. GreenSock Animation API (GSAP)
    7. đź›  Off-canvas menu: Animations
    8. đź›  Modal: Animating the modal
    9. đź›  Modal: Animating the pointing hand
    10. đź›  Modal: Animating the waving hand
    11. đź›  Modal: Wave hand animation with JavaScript (using GSAP)
    12. đź›  Accordion: Animations
    13. đź›  Carousel: Animations
  8. Useful JS features
    1. Ternary operators
    2. AND and OR operators
    3. Early returns
    4. Template Literals
    5. Destructuring
    6. Default parameters
    7. Enhanced Object Literals
    8. Rest and Spread
    9. Useful array methods
    10. Looping through objects
    11. Returning objects with implicit return
    12. đź›  Accordion: Using useful JavaScript features
    13. đź›  Tabby: Using useful JavaScript features
    14. đź›  Carousel: Useful JavaScript features
  9. JS Best practices
    1. Write declarative code
    2. Functions with a purpose
    3. Manage scope
    4. Reduce state changes
    5. Don't reassign
    6. Don't mutate
    7. Preventing Objects from mutating
    8. Preventing Arrays from mutating
    9. Write pure functions
    10. đź›  Accordion: Refactor
    11. đź›  Carousel: First refactor
    12. đź›  Carousel: Refactoring the dots part
    13. đź›  Carousel: Previous and next buttons
    14. đź›  Carousel: Second refactor
  10. Manipulating text and content
    1. Changing Text and HTML
    2. Creating HTML Elements
    3. Adding multiple elements to the DOM
    4. Removing Elements from the DOM
    5. đź›  Carousel: Creating dots with JavaScript
    6. 🛠️ Calculator: HTML and CSS
    7. 🛠️ Calculator: Happy Path
    8. 🛠️ Calculator: Testing the Happy Path
    9. 🛠️ Calculator: Easy Edge Cases
    10. 🛠️ Calculator: Difficult Edge Cases
    11. 🛠️ Calculator: Refactoring
    12. The switch statement
    13. 🛠️ Calculator: Refactoring (Part 2)
    14. 🛠️ Popover: Making one popover
    15. 🛠️ Popover: Making four popovers
    16. 🛠️ Popover: Making popovers with JavaScript
  11. Handling Forms
    1. Intro to forms
    2. Selecting form fields with JavaScript
    3. Form fields and their events
    4. Sanitize your output
    5. Generating unique IDs
    6. 🛠️ Popover: Dynamic ID
    7. 🛠️ Todolist: The HTML and CSS
    8. 🛠️ Todolist: Creating tasks with JavaScript
    9. 🛠️ Todolist: Deleting tasks with JavaScript
    10. 🛠️ Typeahead: The HTML and CSS
    11. 🛠️ Typeahead: Displaying predictions
    12. 🛠️ Typeahead: Selecting a prediction
    13. 🛠️ Typeahead: Bolding search terms
  12. Handling Dates
    1. The Date object
    2. Getting a formatted date
    3. Getting the time
    4. Local time and UTC Time
    5. Setting a specific date
    6. Setting a date with Date methods
    7. Adding (or subtracting) date and time
    8. Comparing Dates and times
    9. 🛠️ Datepicker: HTML and CSS
    10. 🛠️ Datepicker: Building the calendar
    11. 🛠️ Datepicker: Building the datepicker with JavaScript
    12. 🛠️ Datepicker: Previous and Next buttons
    13. 🛠️ Datepicker: Selecting a date
    14. 🛠️ Datepicker: Positioning the datepicker
    15. 🛠️ Datepicker: Showing and hiding
    16. Formatting a date with toLocaleString
    17. setTimeout
    18. setInterval
    19. 🛠️ Countdown timer: HTML and CSS
    20. 🛠️ Countdown timer: JavaScript
    21. 🛠️ Countdown timer: Counting Months
    22. 🛠️ Countdown timer: Daylight Saving Time
    23. 🛠️ Countdown timer: Counting Years
  13. Async JS
    1. Introduction to Ajax
    2. Understanding JSON
    3. The Fetch API
    4. Possible data types
    5. JavaScript Promises
    6. Requests and responses
    7. Sending a POST request
    8. Authentication
    9. Handling errors
    10. Viewing response headers
    11. CORS and JSONP
    12. XHR vs Fetch
    13. Using an Ajax library
    14. Reading API documentation
    15. Understanding curl
    16. 🛠️ Todolist: The Todolist API
    17. 🛠️ Todolist: Fetching tasks
    18. 🛠️ Todolist: Creating tasks
    19. 🛠️ Todolist: Editing tasks
    20. 🛠️ Todolist: Deleting tasks
    21. 🛠️ Todolist: Creating tasks with Optimistic UI
    22. 🛠️ Todolist: Handling Optimistic UI errors
    23. 🛠️ Todolist: Editing tasks with Optimistic UI
    24. 🛠️ Todolist: Deleting tasks with Optimistic UI
    25. 🛠️ Todolist: Refactor
    26. 🛠️ Typeahead: How to add Ajax
    27. 🛠️ Typeahead: Adding Ajax
    28. 🛠️ Typeahead: Handling errors
    29. 🛠️ Google Maps Clone: Creating your first Google Map
    30. 🛠️ Google Maps Clone: Fetching JSONP via JavaScript
    31. 🛠️ Google Maps Clone: Drawing directions
    32. 🛠️ Google Maps Clone: Driving directions
    33. 🛠️ Google Maps Clone: Handling errors
    34. 🛠️ Google Maps Clone: Adding stopovers
    35. 🛠️ Google Maps Clone: Refactor
  14. Advanced Async JS
    1. Requesting many resources at once
    2. Asynchronous functions
    3. Handling multiple awaits
    4. Asynchronous loops
    5. 🛠️ Dota Heroes: Listing heroes
    6. 🛠️ Dota Heroes: Filtering heroes (Part 1)
    7. 🛠️ Dota Heroes: Filtering heroes (Part 2)
    8. 🛠️ Dota Heroes: Refactoring
    9. 🛠️ Dota Heroes: Hero Page
    10. 🛠️ Dota Heroes: Making the hero page robust
    11. 🛠️ Dota Heroes: Heroes page refactor
  15. Handling Keyboard Events
    1. Keyboard users
    2. Handling commonly used keys
    3. Keyboard events
    4. Understanding Tabindex
    5. Detecting the focused element
    6. Directing focus
    7. Preventing people from tabbing into elements
    8. How to choose keyboard shortcuts
    9. Creating single-key shortcuts
    10. 🛠️ Off-canvas: Adding keyboard interaction
    11. 🛠️ Modal: Adding keyboard interaction
    12. 🛠️ Accordion: Adding keyboard interaction
    13. 🛠️ Tabby: Adding keyboard interaction
    14. 🛠️ Tabby: Refactoring
    15. 🛠️ Carousel: Adding keyboard interaction
    16. 🛠️ Carousel: Displaying help text
    17. 🛠️ Calculator: Adding keyboard interaction
    18. 🛠️ Popover: Keyboard
    19. 🛠️ Popover: Refactor
    20. Keyboard shortcuts with Command and Control modifiers
    21. 🛠️ Todolist: Keyboard
    22. 🛠️ Typeahead: Keyboard
    23. 🛠️ Typeahead: Selecting a prediction with the keyboard
    24. 🛠️ Google Maps Clone: Keyboard
    25. 🛠️ Dota Heroes: Keyboard
    26. 🛠️ Datepicker: Tabbing in and out
    27. 🛠️ Datepicker: Keyboard shortcuts
  16. Screen reader accessibility
    1. What is accessibility?
    2. How to use a screen reader
    3. Using NVDA
    4. Using Voiceover
    5. Aria roles
    6. Landmark roles
    7. Document structure roles
    8. Live region roles
    9. Widget roles
    10. Window and Abstract roles
    11. Accessible names and descriptions
    12. Hiding content
    13. ARIA properties and ARIA states
    14. ARIA for expandable widgets
    15. 🛠️ Off-canvas: Accessibility
    16. ARIA for modal dialogs
    17. 🛠️ Modal: Screen reader accessibility
    18. 🛠️ Accordion: Screen reader accessibility
    19. ARIA for Tabbed components
    20. 🛠️ Tabby: Screen reader accessibility
    21. 🛠️ Tabby: Refactor
    22. 🛠️ Carousel: Screen reader accessibility
    23. Roles that trigger Forms and Application modes
    24. What's next for accessibility?
  17. Handling Scroll
    1. The Scroll event
    2. 🛠️ Auto-hiding Sticky-nav: HTML and CSS
    3. 🛠️ Auto-hiding Sticky-nav: JavaScript
    4. 🛠️ Auto-hiding Sticky-nav: Natural reveal
    5. Intersection Observer API
    6. Intersection Observer Options
    7. 🛠️ Slide & Reveal
    8. 🛠️ Slide & Reveal: Always fade-in when you scroll down
    9. 🛠️ Slide & Reveal: Fine-tuning the animation
    10. 🛠️ Infinite Scroll: Anatomy
    11. 🛠️ Infinite Scroll: Infinite load
    12. 🛠️ Infinite Scroll: Refactor
    13. 🛠️ Infinite Scroll: Implementing the Infinite Scroll
  18. Mouse, Touch, and Pointer events
    1. Mouse Events
    2. 🛠️ Spinning Pacman: HTML and CSS
    3. 🛠️ Spinning Pacman: JavaScript
    4. Touch events
    5. Pointer events
    6. Touch-action
    7. 🛠️ Spinning Pacman: Supporting Touch
    8. Cloning elements
    9. 🛠️ DragDrop: HTML and CSS
    10. 🛠️ DragDrop: JavaScript
    11. 🛠️ DragDrop: Creating a drop preview
    12. 🛠️ DragDrop: Sortable drop preview
    13. 🛠️ DragDrop: Robustness
    14. 🛠️ DragDrop: Refactor
  19. Object Oriented Programming
    1. Before we begin
    2. What is Object Oriented Programming?
    3. Four Flavours of Object Oriented Programming
    4. Inheritance
    5. This in JavaScript
    6. Call, bind, apply
    7. Creating Derivative Objects
    8. Composition vs Inheritance
    9. Polymorphism
    10. Encapsulation
    11. Closures
    12. Encapsulation in Object Oriented Programming
    13. Getters and Setters
    14. What OOP flavour to use
    15. When to use Object Oriented Programming
  20. Writing reusable code
    1. Creating reusable code by writing libraries
    2. Two Types of libraries
    3. Including libraries with Script tags
    4. Including libraries with ES6 Modules
    5. Dynamic imports
    6. 🛠️ Off Canvas: Building a Library
    7. 🛠️ Modal: Library setup
    8. 🛠️ Modal: Opening the Modal
    9. 🛠️ Modal: Closing the modal
    10. 🛠️ Modal: Inheritance and Polymorphism
    11. 🛠️ Modal: Resolving differences between subclasses
    12. 🛠️ Modal: Exposing properties and methods
    13. 🛠️ Accordion: Building a library
    14. 🛠️ Tabby: Building a library
    15. 🛠️ Carousel: Building a library
    16. 🛠️ Calculator: Library
    17. 🛠️ Calculator: Fixing the Clear Key
    18. 🛠️ Calculator: Handling other keys
    19. 🛠️ Calculator: State
    20. 🛠️ Popover: Library
    21. 🛠️ Popover: Adding event listeners
    22. 🛠️ Typeahead: Library
    23. 🛠️ DatePicker: Library
  21. Going from Vanilla JS to JS Frameworks
    1. 🛠️ Building a Tiny framework
    2. 🛠️ Tiny: Add event listeners
    3. 🛠️ Tiny: Updating state
    4. 🛠️ Tiny: Rendering Child Components
    5. 🛠️ Tiny: Changing Parent State
    6. 🛠️ Tiny: Passing Props
    7. 🛠️ Tiny: Multiple Props
    8. 🛠️ Tiny: Passing values from sibling components
    9. 🛠️ Tiny: Mounting
    10. 🛠️ Tiny: Passing props to descendants
    11. 🛠️ Tiny: A tiny refactor
  22. Single Page Apps
    1. What is a Single Page App?
    2. Simple SPA using only CSS
    3. The Location Interface
    4. The History Interface
    5. Minimum viable server for a SPA
    6. 🛠️ Dota SPA: Introduction
    7. 🛠️ Dota SPA: Building The Heroes List
    8. 🛠️ Dota SPA: Building the filters
    9. 🛠️ Dota SPA: Filtering heroes
    10. 🛠️ Dota SPA: Displaying filtered heroes
    11. 🛠️ Dota SPA: Getting Ready to build the Hero Page
    12. 🛠️ Dota SPA: Building the hero page
    13. 🛠️ Dota SPA: Lore and abilities
    14. 🛠️ Dota SPA: Routing for Single-page apps

🛠️ Todolist: Handling Optimistic UI errors

Requests don’t fail much. If they fail, they fail because of these two reasons:

  1. Connection errors
  2. Servers returning errors

Connection errors

You won’t be able to send requests or receive responses when you’re offline.

Try sending a request without internet connection. You’ll see an error like this (assuming you’ve downloaded zlFetch onto your computer and linked it to your index.html file).

<body>
<!-- Linked zlFetch locally -->
<script src="js/zl-fetch.js"></script>
<script src="js/main.js"></script>
</body>
zlFetch('https://api.learnjavascript.today/users/transporterduo')
.then(response => {
console.log(response)
})
.catch(error => console.error(error))
Fetch error message without internet connection

You also won’t be able to receive a response from a request if your internet connection gets cut off midway.

One way to simulate a cut-off in connection is to disconnect your Wifi while sending a request.

// 10.255.255.1 gives you time to disconnect your wifi
zlFetch('http://10.255.255.1')
.then(response => {
console.log(response)
})
.catch(error => console.error(error))

You’ll get an error message that looks like this:

Fetch error message when the internet connection cuts off.

In both cases, you’ll get TypeError: Failed to fetch as your error message. You won’t be able to get the net:: part in JavaScript.

Handling connection errors

Some apps handle connection errors by telling users they’re offline. Slack does this, for example.

Slack’s warning message when the user is offline.

We can copy Slack and tell users they’re offline too.

First, we’ll use navigator.onLine to check whether a user is online. If the user is online, navigator.onLine return true. If the user is offline, navigator.onLine returns false

console.log(navigator.onLine) // true or false, depending on whether you're online or offline

Second, we’ll adjust the error message depending on whether the user is online.

todolist.addEventListener('submit', ev => {
// ...
zlFetch(/*...*/)
.then(/*...*/)
.catch(_ => {
// ...
const errorMessage = navigator.onLine
? 'Cannot add task. Please try again later.'
: `It seems like you're offline. Please go online to use the Todolist.`
// ...
})
})

If the user goes offline while sending a request, they’ll see this message:

Offline error message

If they’re online, they’ll see this message:

Online error message

A better way to handle connection errors

We don’t have to wait for a user to send a request before we check if they’re offline. We can tell whether they’re online or offline anytime with two events.

  1. online: Fires when user comes online
  2. offline: Fires when user goes offline

We can build a warning message to inform users when the moment they go offline. It’s friendly compared to an error message.

Offline warning message.

We can build the warning message with the following HTML:

<div class="flash-container">
<div class="flash flash--connection" data-type="warning">
<svg class="flash__icon"><!-- ... --></svg>
<span class="flash__message"
>It seems like you're offline. Please go online to use the Todolist.</span
>
<button class="flash__close"><!-- ... --></button>
</div>
</div>

We’ll only show the message when the user is offline. To do this, we can add a custom attribute called data-connection-status to the <body> element.

navigator.onLine
? (document.body.dataset.connectionStatus = 'online')
: (document.body.dataset.connectionStatus = 'offline')

And we can use the following CSS to show or hide the warning message.

.flash--connection {
visibility: hidden;
}
[data-connection-status='offline'] .flash--connection {
visibility: visible;
}

If a user goes offline when they’re using the Todolist, they’ll trigger an offline event. Likewise, if they come online when they’re using the Todolist, they’ll trigger an online event.

We’ll use the events to update the connection status.

function setConnectionStatus() {
navigator.onLine
? (document.body.dataset.connectionStatus = 'online')
: (document.body.dataset.connectionStatus = 'offline')
}
setConnectionStatus()
window.addEventListener('online', setConnectionStatus)
window.addEventListener('offline', setConnectionStatus)
Toggling between online and offline states.

Since we have a message that warns the user when they’re offline, we can remove connection errors from the error handler.

todolist.addEventListener('submit', event => {
// ...
zlFetch(/*...*/)
.then(/*...*/)
.catch(_ => {
// ...
const errorMessage = 'Cannot add task. Please try again later.'
// ...
})
})

If you go offline and refresh the Todolist, you’ll see a list of error messages. You get these errors because the browser can’t fetch libraries when you’re offline. (You can’t send requests or receive responses. Remember?)

Error requesting libraries

You can mitigate these errors by downloading the libraries into your project. (Highly recommended for real projects).

Anyway, the zlFetch is not defined error prevents the rest of the JavaScript file from executing. If you want online/offline code to work, you’ll want to put them at the start of the JavaScript file.

// Put these at the start of your JavaScript file
setConnectionStatus()
window.addEventListener('online', setConnectionStatus)
window.addEventListener('offline', setConnectionStatus)

Server errors

Servers return errors because of three reasons:

  1. The browser can’t reach the server
  2. Something went wrong in the server
  3. Client errors

When the browser can’t reach the server

It’s a connection error when the browser can’t reach the server. You’ll also get an error message that says TypeError: Failed to fetch. This happens even if the server goes offline.

Fetch error when it fails to reach server.

In this case, we don’t know why we can’t reach the server. The best error message we can say is Failed to reach server. It’s more friendly compared to TypeError: Failed to fetch.

todolist.addEventListener('submit', event => {
// ...
zlFetch(/*...*/)
.then(/*...*/)
.catch(error => {
// ...
let errorMessage = ''
const { message } = error.body
if ((message = 'TypeError: Failed to fetch')) {
errorMessage = 'Failed to reach server. Please try again later.'
} else {
errorMessage = 'Cannot add task. Please try again later.'
}
// ...
})
})

I usually to add a Please try again later message just incase something went wrong with the connection temporarily. If the user gets the Please try again later message in two different occasions, they’ll usually contact me so I can fix the problem.

Something went wrong with the server

Developers who write code for servers can make mistakes too. If something goes wrong inside the server (that has nothing to do with your request), the server should return a 500+ Internal Server Error.

We don’t know what error messages might come from the server in this case. It might be something weird like E11000 duplicated key error if the developer did not send a proper error message.

What we can do is use the error message from the server as a default. If we notice a specific error message later, we can replace it with our own (like the TypeError one).

todolist.addEventListener('submit', event => {
// ...
zlFetch(/*...*/)
.then(/*...*/)
.catch(error => {
// ...
if ((message = 'TypeError: Failed to fetch')) {
errorMessage = 'Failed to reach server. Please try again later.'
} else {
errorMessage = error.body.message
}
// ...
})
})

Client errors

Client errors are 400+ errors. Examples include:

  1. 400 Bad request
  2. 401 Unauthorized
  3. 403 Forbidden
  4. 404 Not found

Again, we don’t know what error messages come from the backend. We can only hope the developer created proper error messages for us.

If you get a friendly error message, you can use the error message directly. For example, if you send in a Bad Request, you’ll get a friendly error message that says Task requires a name.

Response returns with an error.

Sometimes, you don’t get friendly messages. For example, if you sent set a wrong username or password for the Authorization header, you’ll get an error message that says Unauthorized.

Unauthorized error.

Unauthorized isn’t friendly. We can choose to change it up to be slightly more friendly.

todolist.addEventListener('submit', event => {
// ...
zlFetch(/*...*/)
.then(/*...*/)
.catch(error => {
// ...
if ((message = 'TypeError: Failed to fetch')) {
errorMessage = 'Failed to reach server. Please try again later.'
} else if ((message = 'Unauthorized')) {
errorMessage =
'Invalid username or password. Please check your username or password.'
} else {
errorMessage = error.body.message
}
// ...
})
})

That’s it!