A list of all the methods SteamAPI provides is available here.

• CommonJS Modules -> ES Modules
• Import using import statement instead of require()
• SteamAPI constructor now takes false as the first parameter if you don't want to supply a key
• Options for constructor have changes from { enabled, expires, disableWarnings } to { language, currency, headers, baseAPI, baseStore, baseActions, inMemoryCacheEnabled, gameDetailCacheEnabled, gameDetailCacheTTL, userResolveCacheEnabled, userResolveCacheTTL }
• Custom caching may be enabled by setting inMemoryCacheEnabled: false and setting .gameDetailCache/.userResolveCache. Must implement CacheMap interface in src/Cache.ts
• getFeaturedGames() returns object instead of array
• Server#game -> Server#gameDir
• App IDs are passed as numbers not strings (although a string will probably still work)
• Any other changes to the API can be found in https://github.com/xDimGG/node-steamapi/blob/master/PORT.md

• Allow getGameDetails to return either a GameDetails object or a map of string to GameDetails depending on if the user supplied a single id or an array of ids.
• Maybe separate groups of endpoints into different classes so there isn't just a monolithic SteamAPI class? Not quite sure how they would be grouped.
• Add some convenience methods to the Cache class to reduce double logic in SteamAPI.ts

Once signed into Steam, head over to http://steamcommunity.com/dev/apikey to generate an API key.

First, we start by making a SteamAPI "user".

Now, we can call methods on the steam object.

For example, let's retrieve the SteamID64 of a user. SteamAPI provides a resolve method, which accepts URLs and IDs.

Now let's take that ID, and fetch the user's profile.