alkihis
alkihis
Thanks for the quick reply! I agree with your suggestion ; unfortunately, code that causing this kind of query is slightly more complicated than that, but I'm working on fixing...
Hi, Can you give more details by accessing `error.errors`? ``` try { await client.v2.tweet(...) } catch (error) { console.log(error.errors) } ```
This is an issue of Twitter API and not the lib right? The library just takes the ID of posted tweet and gives it to twitter to send the next...
Hi, This may be a problem with the parsing of rate limit headers. Either Twitter do not return rate limit info for this endpoint, or it's a parsing problem elsewhere....
Fix available in 1.12.5 :)
Socket is already manually closed at the end of a fetch. It seems like it is a similar issue as https://github.com/node-fetch/node-fetch/issues/1479 (this package uses the same HTTP logic as node-fetch)....
Hello, Thank you for the detailed report. Unfortunately, I couldn't manage to reproduce (with macOS). By looking at the code, everything is closed correctly (on Node.js side) and I don't...
Considering this package hasn't any public dependencies, `npm audit` result don't make sense, only dev packages are affected. I can accept it but can you please generate the lockfile in...
Hi, Personally I prefer to see this as a GitHub action, git hooks are really intrusive.
Thanks for the report! Ah, if only Twitter response data could be consistent 🥲 I'll look how I can type/parse that without breaking anything.