James Q Quick

Posted on Sep 3, 2019 • Originally published at jamesqquick.com on Sep 3, 2019

Build a Pokedex with Vanilla JavaScript

#javascript #html #css #webdev

Front-end frameworks like React get lots of attention, but you don't always need one. In this article, I'm going to combine my love for two things, JavaScript and Pokemon. We are going to build a Pokedex for the original 150 pokemon using vanilla HTML, CSS, and JavaScript.

Check out the Codepen for source code!

Scaffold the Project

This project will not have many files, namely an index.html , app.css , and an app.js. That said, to get started, create a folder on your computer and open it with your favorite editor. Mine is VS Code!

With the folder open, you'll need to create the three files from above.

index.html
app.css
app.js

Try out the VS Code extension Web Boilerplate, which can generate these three files for you

With these files created, you'll now need to link to the CSS and JavaScript files inside of the index.html. Your HTML code will look like this.

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta http-equiv="X-UA-Compatible" content="ie=edge" />
    <title>Quick's Pokedex</title>
    <link rel="stylesheet" href="app.css" />
  </head>
  <body>
    <script src="app.js"></script>
  </body>
</html>

With the boilerplate code taken care of, we can start to add a bit of content to the page. Start by adding a div with a class of container inside of the body. This is where we will put all our content.

Inside of the container div, add an h1 element with the name of your app. I call mine "Quick's Pokedex". Lastly, add an ol element with an id of pokedex . This ordered list is where we are going to display all the Pokemon information.

Here's what your HTML file should look like.

<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta http-equiv="X-UA-Compatible" content="ie=edge" />
    <title>Quick's Pokedex</title>
    <link rel="stylesheet" href="app.css" />
    <link
      href="https://fonts.googleapis.com/css?family=Rubik&display=swap"
      rel="stylesheet"
    />
  </head>
  <body>
    <div class="container">
      <h1>Quick's Pokedex</h1>
      <ol id="pokedex"></ol>
    </div>
    <script src="app.js"></script>
  </body>
</html>

Fetch Pokemon Data using the PokeAPI

Believe it or not that's everything we will add to the HTML page. Now, we move on to JavaScript where we will load Pokemon data from the PokeAPI. To do this, we will use JavaScript Fetch to make HTTP requests to the API.

For a refresher on the Fetch API, check out JavaScript Fetch API - Getting Started!

Let's start by looking at how the API works. To get information about a specific Pokemon, you make the request and pass the id of that Pokemon. So, if you want to get information about Bulbasaur (number 1), you would make the request adding 1 to the end like so.

https://pokeapi.co/api/v2/pokemon/1

This works well enough, but we are going to want information about 150 Pokemon, not just one. To do this, we can iterate through numbers 1-150 and make the API request for each one. Here's a snippet of what this might look like.

for (let i = 1; i <= 150; i++) {
  const url = `https://pokeapi.co/api/v2/pokemon/${i}`;
  fetch(url)
    .then(res => res.json())
    .then(pokemon => {
      console.log(pokemon);
    });
}

Here's a couple of things to notice in that code. We used ES6 template literal strings to append the value of i (the index) to the end of each request. Also, we had to convert the initial Fetch response to a JavaScript object by calling res.json(). We use "promise chaining" to accomplish this.

For a refresher on JavaScript promises, check out JavaScript Promises - Getting Started

In the end, we get access to the pokemon variable which holds the data for the pokemon. There's one big problem here though. This is a very inefficient way to make so many API requests. Because the API call is inside of a For Loop, we have to wait for each one to finish before making the next.

Typically, you shouldn't make asynchronous calls inside of a For Loop.

We can update this by using Promise.all(). Promise.all() allows us to run asynchronous API calls in parallel instead of sequentially. This means that the time it takes to make 150 requests will be about the same as making 1! That's a drastic improvement!

Here's what the code for this looks like.

const promises = [];
for (let i = 1; i <= 150; i++) {
  const url = `https://pokeapi.co/api/v2/pokemon/${i}`;
  promises.push(fetch(url).then(res => res.json()));
}

Promise.all(promises).then(results => {
  console.log(results);
});

This might seem a bit complicated, so let's break down the steps.

Create an empty array to hold the promises
Iterate 1-150
Make the API request which returns a promise
Add that promise to the promises array
Use Promise.all() to wait for all requests to finish (in parallel)
Get access to an array of Pokemon info with the results variable

Converting the Pokemon Data

With the Pokemon data loaded, we now need to convert it to a format that we want to work with. For example, for each Pokemon object that gets returned, there is lots of unnecessary data. We only care about a few properties.

name
id
type
image

In general, we want to convert the array of data from our requests to an array of Pokemon data with only the info above. We can use the Array.map() function to handle this conversion.

Anytime you want to convert each item in an array, think Array.map()!

const pokemon = results.map(data => ({
  name: data.name,
  id: data.id,
  image: data.sprites["front_default"],
  type: data.types.map(type => type.type.name).join(", "),
}));

As you can see, we retrieved most of the data we need without much effort. Yet, the type data is not so easy. The incoming Pokemon data represents types as an array, but we want a comma separated string. For this conversion, we can use the map() Array function combined with a join() String function .

type: data.types.map(type => type.type.name).join(", ");

Display Pokemon Data

Now that we have the converted Pokemon data, it's time to display it on the screen. It might seem a bit odd, but we will do this by generating an HTML string using JavaScript. This string represents the HTML content to go inside of the ol element. Here are the steps we are going to follow.

Create a function called displayPokemon
Call this function from fetchPokemon passing the Pokemon data as the parameter
Use Array map() to convert each Pokemon object to an li element string
Use String join() to join all the element strings
Get a reference to the ol element in JavaScript
Set the innerHTML of the ol element to the generated string

Start by creating a function called displayPokemon that takes a parameter called pokemon.

const displayPokemon = pokemon => {};

Call the new function from within fetchPokemon. Make sure to pass the pokemon variable as the parameter.

Promise.all(promises).then(results => {
  const pokemon = results.map(data => ({
    name: data.name,
    id: data.id,
    image: data.sprites["front_default"],
    type: data.types.map(type => type.type.name).join(", "),
  }));
  displayPokemon(pokemon);
});

Now, we will generate the HTML string by using map() and join(). Because we are using ES6 Template Literal strings we can do a couple of useful things. We can have the string span many lines and keep correct formatting. We can also inject variables into the string using string interpolation. Lastly, notice that we are applying classes to the elements that we create. We will use these classes to add style in the next section.

const pokemonHTMLString = pokemon
  .map(
    pokeman =>
      `
    <li class="card">
        <img class="card-image" src="${pokeman.image}"/>
        <h2 class="card-title">${pokeman.id}. ${pokeman.name}</h2>
        <p class="card-subtitle">Type: ${pokeman.type}</p>
    </li>
    `
  )
  .join("");

At the top of the file, you will need to get a reference in JavaScript to the ol element with an id of pokedex.

const pokedex = document.getElementById("pokedex");

Now, set the innerHTML of the ol element to the HTML string that we generated.

pokedex.innerHTML = pokemonHTMLString;

Here's what the entire function looks like.

const displayPokemon = pokemon => {
  console.log(pokemon);
  const pokemonHTMLString = pokemon
    .map(
      pokeman =>
        `
    <li class="card">
        <img class="card-image" src="${pokeman.image}"/>
        <h2 class="card-title">${pokeman.id}. ${pokeman.name}</h2>
        <p class="card-subtitle">Type: ${pokeman.type}</p>
    </li>
    `
    )
    .join("");
  pokedex.innerHTML = pokemonHTMLString;
};

Style Pokemon Cards

All the Pokemon data is being displayed now, but it's not pretty! Let's jump into the css to start adding some styles.

Let's start by adding some basic styles to the body, mainly for font and background color.

body {
  background-color: orangered;
  margin: 0;
  font-family: rubik;
  color: white;
}

For the font, I'm referencing a Google font called Rubik. If you want to use it as well, you'll need to add the following line to the head section of your HTML file.

<link
  href="https://fonts.googleapis.com/css?family=Rubik&display=swap"
  rel="stylesheet"
/>

Next, we can add some style to our content container. This will give some breathing room to the content.

.container {
  padding: 40px;
  margin: 0 auto;
}

We also will add a bit of styling to the title of the app.

h1 {
  text-transform: uppercase;
  text-align: center;
  font-size: 54px;
}

Then, we add the base styles for the Pokedex "cards".

.card {
  list-style: none;
  padding: 40px;
  background-color: #f4f4f4;
  color: #222;
  text-align: center;
}

.card-title {
  text-transform: uppercase;
  font-size: 32px;
  font-weight: normal;
  margin-bottom: 0;
}

.card-subtitle {
  font-weight: lighter;
  color: #666;
  margin-top: 5px;
}

.card-image {
  height: 180px;
}

Those are starting to look a bit better, but we want to be able to display the grid as a grid that will adapt to screen sizes. To do this, we will use CSS Grid. We won't go into much detail of CSS Grid here. . If you are looking for additional material, I recommend these two resources.

CSS Grid from Wes Bos
Practical CSS Grid by Bryan Robinson

In general, we want to display the cards horizontally with each having a minimum width of 320px. If the widths become to big for the screen, cards should wrap to the next row. We can achieve this with the following styles.

#pokedex {
  padding-inline-start: 0;
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(320px, 1fr));
  grid-gap: 20px;
}

Animate Pokemon Card on Hover

The very last thing we will do in this tutorial is add an animation to the Pokemon when the user hovers on one. This adds a fun touch of interaction when someone is scrolling through.

Let's apply an animation to the card on hover.

.card:hover {
  animation: bounce 0.5s linear;
}

Now, we need to create the animation. It will be a simple bounce effect. This animation will move the card up and back down twice.

@keyframes bounce {
  20% {
    transform: translateY(-6px);
  }
  40% {
    transform: translateY(0px);
  }
  60% {
    transform: translateY(-2px);
  }
  80% {
    transform: translateY(-0px);
  }
}

Wrap Up

That's it. You should have a functioning Pokedex, created with Vanilla HTML, CSS, and JavaScript. See, you don't always need a framework to create something fun!

Top comments (6)

Lee Warrick • Sep 3 '19

Great article!

If I might make a suggestion...

It might not a good idea to do 150 api calls all at once! I could see quickly hitting the rate limit.

If you used https://pokeapi.co/api/v2/pokemon?limit=150 you could get the names for the 150 pokemon, and for the images you could use the index from the returned urls and plug that into: https://raw.githubusercontent.com/PokeAPI/sprites/master/sprites/pokemon/<index number>.png

This wouldn't net you all the types like you have on your example in codepen, but might save you from getting rate-limited from the API.

You could also try attaching the calls to a scroll event so you're only pulling the next few pokemon as a user scrolls down the page. The API supports pagination and even gives you the "next" url to call for the next group of pokemon.

In any case, keep up the good work!

James Q Quick • Sep 4 '19

Wow, really great feedback! I love the thoughts. For the 150 calls, yes I agree it's a little excessive. I was in fact making the request for each Pokemon to get more detailed info, but as you pointed out, I'm missing the type info. I'm thinking I might create a part two and optimize this with a pokemon detail page for further detail.

Thanks again for the commend and suggestions!

Fabian • Sep 4 '19

I look forward to building this and perhaps a v2 in future too! Thanks for the post

James Q Quick • Sep 5 '19

Awesome! Yes, I'm definitely planning on a part 2!

G M Ashiqur Rahaman • Sep 4 '19

Hey James Yesterday i saw your Youtube video about this and this is Great. I learned so much. By the way i'm kinda noob in JS world. Still learning. Also learn and clear my brain about fetch, promises concept from your other videos . Keep Going 👍

James Q Quick • Sep 5 '19

Awesome, so glad that you enjoyed it and the video helped as well. These are the comments I love to see :)

DEV Community

Build a Pokedex with Vanilla JavaScript

Scaffold the Project

Fetch Pokemon Data using the PokeAPI

Converting the Pokemon Data

Display Pokemon Data

Style Pokemon Cards

Animate Pokemon Card on Hover

Wrap Up

Top comments (6)

Read next

Deployment of a Node.js Application on AWS

How to run cypress run and cypress open at a time

Optimizing React Re-Renders: Best Practices for Performance

Store UI State in localStorage with Stimulus