lolapi | API for LoL stats | REST library

Shouldn't it get directed to '/na1' route?

No, the path clearly doesn't match. Your route expects a single path and the URL you're accessing has multiple.

If you want a catch all then you would need

Using Promise.all to wait for all the "gameData" as follows - also use Array#map to avoid having to push to an array

Note: however, that if there's any rejection in any lolapi.Match.get promise, the Promise.all will reject - this may not be what you want, I'm not sure from your code example

You have another portion of async code in your proimse body (well I assume it is async based on your results):

When you do something asynchronously, it means the function is called at some point in the future. Your call to redis.exists means at some point in the future, the function you provide will be called. The line after it, console.log(summonerData), is run before the callback function.

Move console.log(summonerData) into the function for it to work as you intend.

Yes, it's an async issue. The usual dupetarget is How do I return the response from an asynchronous call? and it's worth reading the answers there, but you have a couple of things going on here which I think deserve addressing directly:

Your lolapi.Match.get completion is called asynchronously, so:

1. You can't expect the calls' callbacks to have been called before the for loop is over (in fact, you're guaranteeed that they won't have been called), and

2. i won't have the value you expect it to have when saving to gameData, because it will already have been incremented all the way to matchIds.length before the first callback occurs.

So you want to have the callback close over something other than i, and also have a way to keep track of how many callbacks you've gotten (since they can occur out of order, so we can't use gameData.length):