Johan Preynat

@ianhattendorf > I'll see what we can do about getting prebuilts out soon for Node 16. Thanks for your work on nodegit. It would be awesome to have the binaries...

Actually, the issue seems worst than only that: ```js gm.test('---\nSome text'); // true ``` ```js gm('---\nSome text'); // { content: '', data: 'Some text', isEmpty: false, excerpt: '' } ```

Agreed. This is a **huge** limitation. We have a specific Node module that requires preinstalled binaries (`krb5-config`) to compile through node-gyp, and there's nothing we can do about it because...

Our team would also be interested in this kind of feature 👍 The main reason for us is also to allow for better caching, especially of 3rd party modules that...

@Haroenv Any news on this PR? It'd be great to have this released to fix #1035

Thanks for the suggestion @Haroenv. But sadly we already tried using `withinHeaders` and we have some cases where the limit is too small for us, preventing us from switching from...

We also encounter the same error when switching to the client v4. On our end, we encounter the `Header too large` ApiError and have to use the [proposed workaround](https://github.com/algolia/algoliasearch-client-javascript/issues/1035#issuecomment-592014999) by...

Hi @Haroenv, it wasn't an issue with the URL but the size of the header. I got this issue as soon as I switched from v3 to v4 when calling...

Actually, the workaround is working from our Node backend, but from the frontend, no results are returned anymore, so this is definitely problematic for us. I've tried passing the api...

Just fetching the URL with everything in the query parameters returns this error.