@the-convocation/twitter-scraper 0.15.0 → 0.15.1

package/README.md

@@ -171,14 +171,13 @@ const scraper = new Scraper({
 ### Rate limiting
 The Twitter API heavily rate-limits clients, requiring that the scraper has its own
 rate-limit handling to behave predictably when rate-limiting occurs. By default, the
-scraper uses a rate-limiting strategy that rates for the current rate-limiting period
+scraper uses a rate-limiting strategy that waits for the current rate-limiting period
 to expire before resuming requests.
 
 **This has been known to take a very long time, in some cases (up to 13 minutes).**
 
 You may want to change how rate-limiting events are handled, potentially by pooling
-scrapers logged-in to different accounts (approach currently out of scope for this
-README). The rate-limit handling strategy can be configured by passing a custom
+scrapers logged-in to different accounts (refer to [#116](https://github.com/the-convocation/twitter-scraper/pull/116) for how to do this yourself). The rate-limit handling strategy can be configured by passing a custom
 implementation to the `rateLimitStrategy` option in the scraper constructor:
 
 ```ts

package/dist/default/cjs/index.js

@@ -60,8 +60,8 @@ class WaitingRateLimitStrategy {
   }
 }
 class ErrorRateLimitStrategy {
-  onRateLimit({ response: res }) {
-    throw ApiError.fromResponse(res);
+  async onRateLimit({ response: res }) {
+    throw await ApiError.fromResponse(res);
   }
 }