Question 1

How to cache Steam game details with SteamAPI?

Accepted Answer

Enable inMemoryCacheEnabled and gameDetailCacheEnabled in the constructor options, and set gameDetailCacheTTL for expiration. For custom caching, implement the CacheMap interface as described in the docs.

Question 2

SteamAPI vs steam-user: which is better for Node.js?

Accepted Answer

SteamAPI wraps the Steam Web API for fetching data like profiles and games, while steam-user handles Steam client protocol for things like logging in. Choose based on whether you need web data or client automation.

Question 3

Does SteamAPI work without an API key?

Accepted Answer

Yes, pass false as the first parameter to the constructor, but methods requiring authentication won't function, limiting access to features like private user data.

Question 4

How to migrate from SteamAPI 2.x to 3.x?

Accepted Answer

Switch from CommonJS to ES Modules with import statements, update constructor options to the new format, and handle API changes like getFeaturedGames returning an object, as detailed in PORT.md.

Question 5

What languages does SteamAPI support for localization?

Accepted Answer

Set language and currency preferences in the constructor to fetch localized data for game details and other endpoints, supporting Steam's available language options.

Question 6

Can I use SteamAPI in a browser?

Accepted Answer

No, it's designed for Node.js and relies on server-side HTTP requests, making it unsuitable for browsers due to CORS restrictions and security risks with API keys.

steamapi

What is steamapi?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions