apify-client-js
apify-client-js copied to clipboard
Apify API client for JavaScript / Node.js.
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [docusaurus-plugin-typedoc-api](https://togithub.com/milesj/docusaurus-plugin-typedoc-api) | [`3.0.0` -> `4.2.0`](https://renovatebot.com/diffs/npm/docusaurus-plugin-typedoc-api/3.0.0/4.2.0) | [](https://docs.renovatebot.com/merge-confidence/)...
- Remove webpack - Bring in a build script similar to https://github.com/apify/apify-shared-js/pull/430 This is gonna be counted as a breaking change I *think*, but it'll have to wait and see...
These are currently missing, so on Console, we have to make regular API calls without the client. It would be better to use the client.
We have an endpoint `/acts/ACTOR-ID/validate-input` which is not implemented in the client, we should implement it. It takes the input to validate as POST payload, and optionally a `build` query...
1. A lot of the properties are `| undefined`. Why? Is there a case where the queue would not have those properties? I think we would need 2 different types,...
https://github.com/apify/apify-client-js/blob/5093b8f98425af8c829478e8df5aeee1d007c283/src/interceptors.ts#L34 https://github.com/apify/apify-client-js/blob/5093b8f98425af8c829478e8df5aeee1d007c283/src/interceptors.ts#L49-L50 https://github.com/apify/apify-client-js/blob/5093b8f98425af8c829478e8df5aeee1d007c283/src/interceptors.ts#L68-L72 I was wondering why I was receiving `{"type":"Buffer","data":[...]}` instead of actual data... This breaks `.call(buffer, { contentType: 'application/json' })`.
From this discussion https://apifier.slack.com/archives/C013WC26144/p1653552365035479, it seems that sometimes there is a series of network errors that lead to a suspicion that the client might be retrying the requests to the...
Node has 512MB limit on string size, if the response from API is larger, the client fails to parse it. I guess the issue might also manifest in key-value-stores? Other...
Currently the KV storages only accepts Buffer or String when you use the library. For big data, it should be handling streams as well. It seems like it is doable...