Releases: PLhery/node-twitter-api-v2
Releases · PLhery/node-twitter-api-v2
1.9.0 - v2 includes helpers
- Feat: Helpers for v2 includes
- Feat: Support for custom debug loggers
- Fix: Errors accessor to get API errors in paginators #145
- Fix: Correctly update .includes/.meta/.errors in paginators when using async iterator #142
- Fix: Incorrect HTTP method for GET lists #147 #148
- Doc: Better doc & examples for OAuth 2.0 user-context
1.8.1 - GET lists v2
- Feat: Add every GET lists v2 endpoints
1.8.0 - OAuth2 user-context
- Feat: Add OAuth2 user-context support
- Feat: Add users/me v2 endpoint wrapper
1.7.2 - Fix paginators for-await-of
- Fix: Paginator can return multiple times the same results in some conditions
- Feat: .done property for paginators, to know when a next page is fetchable
1.7.1
1.7.0 - Post & delete tweets with v2 API
- Feat: Create tweet v2 endpoint (thanks to @sudo-kaizen) #110
- Feat: Delete tweet v2 endpoint (thanks to @sudo-kaizen) #111
- Feat: Tweet thread and reply to a tweet v2
- Fix: BREAKING: Explicitly specify userId on userMutingUsers (thanks to @mika-f) #114
Migrate
userMutingUsers
now requires to give current logged user ID in order to correctly work.
This is due to force v2 endpoints to be completely disconnected from v1 API ; v2 API doesn't yet allow to download currently logged user (no alternative to v1.verifyCredentials()
).
If you have access to v1 API, you can do the following:
const mutedPaginator = await client.v2.userMutingUsers((await client.currentUser()).id_str);
1.6.5
1.6.4
1.6.3 - Stream bug fixes
- Fix: Streams will know correctly reject
.connect
Promise
on connection error ifautoReconnect
isfalse
1.6.2 - Auto stream reconnect for initial connection
- Feat: Streams do now support auto-reconnection for the initial connection attempt