-
Posts
1632 -
Joined
-
Last visited
Posts posted by GitHub
-
-
- Fixed issue where boolean properties of EconItem might not be properly decoded
-
- Fixed an unhandled error that may be thrown if a network error occurs
Full Changelog: v2.11.2...v2.11.3
-
- Fixed "Already logged on" error being thrown when calling logOn() following a proxy connection failure (issue #481)
Full Changelog: v5.0.8...v5.0.9
-
What's Changed
Full Changelog: v2.11.1...v2.11.2
-
-
- Added ability to use an access token against the WebAPI rather than an API key
- See here for more info
- Contributed by @Sadzurami in #345
- Added
minimumPollInterval
option- Contributed by @Sadzurami in #346
- Added
pollFullUpdateInterval
option - Added sanity checks with warnings for polling interval options
Full Changelog: v2.10.6...v2.11.0
- Added ability to use an access token against the WebAPI rather than an API key
-
- Fixed SteamUser automatically reconnecting after
logOff()
is called
Full Changelog: v5.0.7...v5.0.8
- Fixed SteamUser automatically reconnecting after
-
- Fixed
steamID
property not being set when using cookies that have a domain attribute
Full Changelog: v3.48.1...v3.48.2
- Fixed
-
- Fixed cookie issue caused by differing tokens across different Steam domains
Full Changelog: v3.48.0...v3.48.1
-
getWebCookies()
for EAuthTokenPlatformType.WebBrowser now returns cookies for all Steam domains (with; Domain=steamcommunity.com
appended in the cookie string) due to Steam now issuing different tokens for different domains (PR #37 by @Sadzurami)- Most cookie jar libraries should handle this properly, but you may need to check your own app to be sure
Full Changelog: v1.7.1...v1.7.2
-
- Added check to throw an error if you attempt to call logOn() while a log on attempt is already ongoing
Full Changelog: v5.0.6...v5.0.7
-
- Fixed an issue where SteamUser may attempt to reconnect even after emitting
error
due to error during auth
Full Changelog: v5.0.5...v5.0.6
- Fixed an issue where SteamUser may attempt to reconnect even after emitting
-
- Fixed "already logged on" error not having a useful stack trace
Full Changelog: v5.0.4...v5.0.5
-
- BREAKING STEAM CHANGE Mobile confirmation is now required to create a Web API key
- It is now required to have a Steam Guard Mobile Authenticator in order to create a Web API key
getWebApiKey()
no longer attempts to register an API key if your account doesn't yet have onegetWebApiKey()
still works for retrieving your account's existing API keycreateWebApiKey()
has been added to handle creating a new Web API key
Full Changelog: v3.47.1...v3.48.0
Ramifications of This Change
- You now need to enable mobile 2FA to create a Web API key
- You can disable mobile 2FA after your key has been created, and it will keep working
getWebApiKey()
works as before if your account already has a key created, but does not attempt to register a key if you don't yet have one- If you have a script that prepares new accounts for use (e.g. enables 2FA, sets up profile), then you should call
createWebApiKey()
as part of that script, after enabling 2FA. - Any code which consumes
getWebApiKey()
will work as before, provided you create your API key before attempting to call it
- BREAKING STEAM CHANGE Mobile confirmation is now required to create a Web API key
-
- Fixed issue where HTTP requests could hang indefinitely
Full Changelog: v5.0.3...v5.0.4
-
- Fixed pre-connect network errors not being properly handled
Full Changelog: v5.0.2...v5.0.3
-
- Fixed issue where access tokens (cookies) would not be properly refreshed when reusing a LoginSession over a long period of time
Full Changelog: v1.7.0...v1.7.1
-
- Added
clientsessionid
cookie to cookies provided in thewebSession
event- I'm not entirely sure what this does or if it's important, but the Steam client sends it so here we are. It might improve compatibility.
- Updated to use the newer GetCMListForConnect WebAPI method to fetch the Steam server list
- This removes the need to save cm_list.json locally
- Fixed refresh tokens obtained from the
refreshToken
event not working for subsequent logins with error AccessDenied - The correct machine ID is now sent to the auth server when logging in
- This doesn't appear to matter at the moment, but it may have an impact on token validity in the future
Full Changelog: v5.0.1...v5.0.2
- Added
-
- Added ability to pass a custom machine ID when logging on using EAuthTokenPlatformType.SteamClient
Full Changelog: v1.6.0...v1.7.0
-
- Fixed
SteamCommunity.login()
method by having it internally use steam-session- BREAKING: Node.js 12.22.0 or later is required to use
SteamCommunity.login()
(4.0.0 is still working for the rest of the package) - BREAKING: You cannot use
SteamCommunity.login()
if you are also passing a customrequest
instance in to the SteamCommunity constructor due to incompatibility - BREAKING: You will no longer get a
steamguard
value when usingSteamCommunity.login()
- BREAKING: Node.js 12.22.0 or later is required to use
"It's not my fault there's a breaking change in a patch release if Valve already did the breaking!"℠
Full Changelog: v3.47.0...v3.47.1 - Fixed
-
- Added ability to specify a custom user-agent string for WebBrowser logins
Full Changelog: v1.5.0...v1.6.0
-
- Added
localAddress
option for LoginSession and LoginApprover
Full Changelog: v1.4.1...v1.5.0
- Added
-
-
node-steamcommunity v3.48.3
in Releases & Updates
Posted
Full Changelog: v3.48.2...v3.48.3
View on GitHub