Getting data with Axios is easy, but rendering it ~OUCH~

You may know how to fetch data with Axios, but how do you render it in React?

Maybe you tried something like using await in render function to make React wait for your request before rendering. But when you do something like:

  async render() {
    return <>{await axios.get(..)}</>
await in render()

You’ll get an error like this:

Error when using await in render()

Error when using await in render()

Why? Because async operator makes the render function to return a Promise, which is an object and React doesn’t know to render objects.

So, how do you make React wait for your function before render?

Well, the answer is: faking it 😏

Waiting for Axios before rendering

There is a fetching recipe for doing this which is always the same:

  1. Start your component in “loading mode”
  2. *When your component “mounts” *do the request.
  3. When the request is done, save your data and turn off “loading mode”.
  4. Make sure that while your component is in “loading mode”, display a spinner or loading text in your render function. And when not, display your data.

How do you do this in code?

Look at this simple React app that fetches data about a single Pokémon and displays its name and picture:

Pokémon Demo

Example code can be found here

Here is the implementation:

function App() {
  const [isLoading, setLoading] = useState(true);
  const [pokemon, setPokemon] = useState();

  useEffect(() => {
    axios.get("").then(response => {
  }, []);

  if (isLoading) {
    return <div className="App">Loading...</div>;

  return (
    <div className="App">
      <img alt={} src={pokemon.sprites.front_default} />

Load, fetch and display!

How is this translated to our recipe?

1) Start your component in “loading mode”

How to start your component in loading mode

This way you start your component in "loading mode"

With the conditional rendering of “Loading…” text and by using useState we accomplish the “loading mode” state of the component.

**Why are we using useState instead of a simple const? **Because we want to make App component remember this value between renders!

The first render displays “Loading…” in the browser.

2) When your component “mounts” do the request

How to make a request after your component mounts

Mounts → "after render" → accomplished with useEffect

useEffect receives a function that will be called after the DOM (what the browser shows) is updated. Here we tell axios to fetch Charmander data from PokeApi.

axios.get is executed asynchronous, so nothing is changed.

3) When the request is done, save your data and turn off “loading mode”

When request is done, we update the state of our component by using setLoading and setPokemon.

Both calls update the state:

  • setPokemon updates pokemon  from undefined to
  • setLoading updates isLoading from true to false

So… there are 2 renders! 🤯

The second render (triggered by setPokemon) will do nothing in the browser because isLoading is true → component returns “Loading…” again.

The third render (triggered by setLoading) will show Charmander in the browser! Because this time isLoading is false, so we reach the end of the function were the pokemon is finally rendered.

Summing-up this confusing render stuff:


Adding comments in key parts of the code can teach us few things :)

Not familiar with hooks?

Hey! Is 2020, you should! 😂

No problem. Here is the equivalent code with class component:

export default class App extends Component {
  constructor(props) {
    this.state = { isLoading: true, pokemon: undefined };

  componentDidMount() {
    console.debug("After mount! Let's load data from API...");
    axios.get("").then(response => {
      this.setState({ pokemon: });
      this.setState({ isLoading: false });

  render() {
    const { isLoading, pokemon } = this.state;

    if (isLoading) {
      return <div className="App">Loading...</div>;

    return (
      <div className="App">
        <img alt={} src={pokemon.sprites.front_default} />
Code using class components in CodeSandbox

Feeling overwhelmed by React?

React gives you a lot of flexibility to build applications. But too many choices lead us to analysis paralysis, making us spend hours on project configuration instead of building our product.

I created a FREE e-book about good practices to avoid overthinking so you can focus more on building.

✨ Chapters ✨

  1. Code styling and quality.
  2. Organizing your project files.
  3. How to manage your state.