feat(config): Allow options to be passed to algoliasearch (#158)

* feat(config): Add requester param to pass it to algoliasearch to use a corporate proxy

We're using a corporate proxy and cannot make `gatsby-plugin-algolia` work without passing a custom requester.

I found this PR (algolia/algoliasearch-client-javascript#1180) where `createNodeHttpRequester` was extended to pass a custom HTTP agent.
With this change you can pass a custom requester to `gatsby-plugin-algolia` which resolved our issue.

* feat(config): Add param to set the algoliasearch options

* docs(readme): include algoliasearchOptions

Co-authored-by: Haroen Viaene <[email protected]>

Author: bartdeslagmulder

README.md

@@ -95,6 +95,7 @@ module.exports = {
         concurrentQueries: false, // default: true
         skipIndexing: true, // default: false, useful for e.g. preview deploys or local development
         continueOnFailure: false, // default: false, don't fail the build if algolia indexing fails
+        algoliasearchOptions: undefined, // default: { timeouts: { connect: 1, read: 30, write: 30 } }, pass any different options to the algoliasearch constructor
       },
     },
   ],

gatsby-node.js

@@ -41,6 +41,13 @@ exports.onPostBuild = async function ({ graphql, reporter }, config) {
     skipIndexing = false,
     dryRun = false,
     continueOnFailure = false,
+    algoliasearchOptions = {
+      timeouts: {
+        connect: 1,
+        read: 30,
+        write: 30,
+      },
+    },
   } = config;
 
   const activity = reporter.activityTimer(`index to Algolia`);
@@ -69,13 +76,7 @@ exports.onPostBuild = async function ({ graphql, reporter }, config) {
     return;
   }
 
-  const client = algoliasearch(appId, apiKey, {
-    timeouts: {
-      connect: 1,
-      read: 30,
-      write: 30,
-    },
-  });
+  const client = algoliasearch(appId, apiKey, algoliasearchOptions);
 
   activity.setStatus(`${queries.length} queries to index`);