Script Troubleshooting 101

If you were directed to this page after your issue was closed, it was because your issue appeared to be about logic errors in your script rather than a problem with the module.

If you're not 100% sure that it is a bug in the module, refrain from posting issues if you are not prepared to answer the question "what have you tried?" Please try to understand the problem before asking for help; we would like to keep the issue tracker pertaining to bugs with the software instead of personal problems.

Common problems

Script terminates when trying to load an inventory

node-steam-trade does not support the loading of non-existent inventories. Before loading an inventory, make sure it exists by using getContexts.

Script terminates with an error message (TypeError, etc)

If the stack trace does not reference SteamTrade or node-steam-trade.js, it is most definitely not an issue with the module. Review the topmost lines of code that are referenced in the stack trace.

But I think it's a bug!

Before reporting possible bugs to the issue tracker, you should do the following:

• Debug your scripts extensively to ensure it's doing what you expect it to. The most simple way of doing this is to output the contents of variables to the console with console.log().
• Make sure you are using the latest version of the module. Valve have been known to change their internal APIs without warning in the past, so avoid submitting issues that might be caused by using an older version of the module.
• If all else fails, reduce your code as much as possible while retaining a reproducible test case for the problem. This helps isolate the issue if it actually is a bug with the module.