Merge pull request #5134 from segmentio/update-segment-node

Update analytics-node

Author: stayseesong

src/connections/sources/catalog/libraries/server/node/index.md

@@ -282,9 +282,11 @@ Setting | Details
 `maxRetries` _number_ | The number of times to retry flushing a batch. The default is: `3`
 `maxEventsInBatch` _number_ | The number of messages to enqueue before flushing. The default is: `15`
 `flushInterval` _number_ | The number of milliseconds to wait before flushing the queue automatically. The default is: `10000`
-`httpRequestTimeout` | The maximum number of milliseconds to wait for an http request. The default is: `10000`
-`disable` | Disable the analytics library for testing. The default is: `false`
-`httpClient` *Optional* | A custom AnalyticsHTTPClient implementation to support alternate libraries or proxies.  Defaults to global fetch or node-fetch for older versions of node.
+`httpRequestTimeout` _number_ | The maximum number of milliseconds to wait for an http request. The default is: `10000`
+`disable` _boolean_ | Disable the analytics library for testing. The default is: `false`
+`httpClient` _HTTPClient or HTTPClientFn_ | A custom HTTP Client implementation to support alternate libraries or proxies. Defaults to global fetch or node-fetch for older versions of node. See the [Overriding the default HTTP Client](#override-the-default-http-client) section for more details.
+
+See the complete `AnalyticsSettings` interface [here](https://github.com/segmentio/analytics-next/blob/master/packages/node/src/app/settings.ts){:target="_blank"}.
 
 ## Graceful shutdown
 Avoid losing events after shutting down your console. Call `.closeAndFlush()` to stop collecting new events and flush all existing events. If a callback on an event call is included, this also waits for all callbacks to be called, and any of their subsequent promises to be resolved.
@@ -554,7 +556,7 @@ Different parts of your application may require different types of batching, or
 const marketingAnalytics = new Analytics({ writeKey: 'MARKETING_WRITE_KEY' });
 const appAnalytics = new Analytics({ writeKey: 'APP_WRITE_KEY' });
 ```
-## AnalyticsHTTPClient
+## Override the default HTTP Client
 
 Segment attempts to use the global `fetch` implementation if available in order to support several diverse environments.  Some special cases (for example, http proxy) may require a different implementation for http communication.  You can provide a customized wrapper in the Analytics configuration to support this.  Here are a few approaches:
 
@@ -563,21 +565,21 @@ Use a custom fetch-like implementation with proxy (simple, recommended)
 import { HTTPFetchFn } from '../lib/http-client'
 import axios from 'axios'
 
-const httpClient: HTTPFetchFn = async (url, options) => {
-  return axios({
+const httpClient: HTTPFetchFn = async (url, { body, ...options }) =>
+  axios({
     url,
+    data: body,
     proxy: {
-        protocol: 'http',
-        host: 'proxy.example.com',
-        port: 8886,
-        auth: {
-          username: 'user',
-          password: 'pass',
-        },
+      protocol: 'http',
+      host: 'proxy.example.com',
+      port: 8886,
+      auth: {
+        username: 'user',
+        password: 'pass',
       },
+     },
     ...options,
   })
-}
 
 const analytics = new Analytics({
   writeKey: '<YOUR_WRITE_KEY>',
@@ -591,8 +593,8 @@ import { FetchHTTPClient, HTTPClientRequest  } from '@segment/analytics-node'
 class MyClient extends FetchHTTPClient {
   async makeRequest(options: HTTPClientRequest) {
     return super.makeRequest({
-         ...options, 
-         headers: { ...options.headers, foo: 'bar'  }
+        ...options, 
+        headers: { ...options.headers, foo: 'bar' }
       }})
   }
 }