steamcommunity 3.46.1 → 3.47.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (51) hide show
  1. package/LICENSE +21 -21
  2. package/README.md +22 -22
  3. package/classes/CConfirmation.js +37 -37
  4. package/classes/CEconItem.js +120 -120
  5. package/classes/CMarketItem.js +189 -189
  6. package/classes/CMarketSearchResult.js +89 -89
  7. package/classes/CSteamGroup.js +155 -155
  8. package/classes/CSteamUser.js +225 -217
  9. package/components/chat.js +283 -283
  10. package/components/confirmations.js +428 -428
  11. package/components/groups.js +798 -732
  12. package/components/help.js +64 -64
  13. package/components/helpers.js +128 -108
  14. package/components/http.js +150 -150
  15. package/components/inventoryhistory.js +173 -173
  16. package/components/login.js +110 -0
  17. package/components/market.js +387 -387
  18. package/components/profile.js +475 -475
  19. package/components/twofactor.js +152 -152
  20. package/components/users.js +831 -767
  21. package/components/webapi.js +118 -118
  22. package/examples/README.md +35 -35
  23. package/examples/accept_all_confirmations.js +173 -173
  24. package/examples/disable_twofactor.js +135 -135
  25. package/examples/edit-group-announcement.js +118 -118
  26. package/examples/enable_twofactor.js +182 -182
  27. package/index.js +13 -151
  28. package/package.json +11 -6
  29. package/resources/EChatState.js +14 -14
  30. package/resources/EConfirmationType.js +12 -12
  31. package/resources/EFriendRelationship.js +23 -23
  32. package/resources/EPersonaState.js +23 -23
  33. package/resources/EPersonaStateFlag.js +32 -32
  34. package/resources/EResult.js +254 -254
  35. package/.editorconfig +0 -13
  36. package/.github/FUNDING.yml +0 -2
  37. package/.idea/.name +0 -1
  38. package/.idea/codeStyleSettings.xml +0 -13
  39. package/.idea/codeStyles/Project.xml +0 -15
  40. package/.idea/codeStyles/codeStyleConfig.xml +0 -6
  41. package/.idea/copyright/profiles_settings.xml +0 -3
  42. package/.idea/encodings.xml +0 -6
  43. package/.idea/inspectionProfiles/Project_Default.xml +0 -11
  44. package/.idea/jsLibraryMappings.xml +0 -6
  45. package/.idea/misc.xml +0 -6
  46. package/.idea/modules.xml +0 -9
  47. package/.idea/node-steamcommunity.iml +0 -8
  48. package/.idea/steamcommunity.iml +0 -10
  49. package/.idea/vcs.xml +0 -7
  50. package/.idea/watcherTasks.xml +0 -4
  51. package/CONTRIBUTING.md +0 -36
package/.idea/watcherTasks.xml DELETED
@@ -1,4 +0,0 @@
1
- <?xml version="1.0" encoding="UTF-8"?>
2
- <project version="4">
3
- <component name="ProjectTasksOptions" suppressed-tasks="Babel" />
4
- </project>
package/CONTRIBUTING.md DELETED
@@ -1,36 +0,0 @@
1
- # Contributing to SteamCommunity
2
-
3
- Thanks for your interest in making `SteamCommunity` better! I'd appreciate it if you read over this document quickly
4
- before you submit your issue or pull request. It'll make things go much smoother.
5
-
6
- # Issues
7
-
8
- Submitting an issue?
9
-
10
- - If you're **reporting a bug**, please include all relevant details.
11
- - A descriptive title helps for one. Titles of just "Error" or "It doesn't work" really don't help.
12
- - Please describe what you're trying to do, what actually happens, and what you can do to reproduce the problem.
13
- - If you have an error message or a crash, please include the full text of the error message and the stack trace.
14
- - Include the relevant snippet of your code. Wrap it in \`\`\`js /* code */ \`\`\` and GitHub [will format it nicely for you](https://help.github.com/articles/github-flavored-markdown/#syntax-highlighting).
15
- - If you're **requesting a feature**, please be descriptive and understanding.
16
- - A good title makes a difference. Please briefly describe what you're requesting in the title.
17
- - Be descriptive in the issue body, too. Say what you want to do, and ideally what the method should be named.
18
- - Be understanding if I don't think that your feature request falls within the scope of this module.
19
- - If you're **asking a question** or **requesting support**, please don't submit a GitHub issue.
20
- - Issues are only for problems directly relating to the module's code.
21
- - Please [post a thread in the dedicated forum](https://dev.doctormckay.com/forum/8-node-steamcommunity/) instead.
22
-
23
- # Pull Requests
24
-
25
- Submitting a pull request? Great! Thanks for contributing your time and code! Please keep the following in mind.
26
-
27
- - Please follow the existing code style.
28
- - Tabs for indentation
29
- - camelCase for variables and functions
30
- - Opening braces on the same line as the if/for/while statement
31
- - No omitting unnecessary braces
32
- - etc.
33
- - Please avoid breaking changes. If you make a breaking change that can be done in a backwards-compatible manner, I won't accept it.
34
- - Please don't increment the version number in `package.json`. I'll do that myself when I publish it to npm.
35
- - Please include a brief description of your change in the pull request if it's not immediately apparent from the code.
36
- - Be understanding if I don't think that your change falls within the scope of this module.