prepare 3.1.4 release (#290)

## [3.1.4] - 2023-09-06
### Fixed:
- #283 Catch xhr errors on page close and ignore them to reduce noise.

Author: yusinto

CODEOWNERS

@@ -0,0 +1,2 @@
+# Repository Maintainers
+* @launchdarkly/team-sdk

README.md

@@ -4,7 +4,7 @@
 
 ## LaunchDarkly overview
 
-[LaunchDarkly](https://www.launchdarkly.com) is a feature management platform that serves over 100 billion feature flags daily to help teams build better software, faster. [Get started](https://docs.launchdarkly.com/home/getting-started) using LaunchDarkly today!
+[LaunchDarkly](https://www.launchdarkly.com) is a feature management platform that serves trillions of feature flags daily to help teams build better software, faster. [Get started](https://docs.launchdarkly.com/home/getting-started) using LaunchDarkly today!
 
 [![Twitter Follow](https://img.shields.io/twitter/follow/launchdarkly.svg?style=social&label=Follow&maxAge=2592000)](https://twitter.com/intent/follow?screen_name=launchdarkly)
 
@@ -30,7 +30,7 @@ By default, the SDK sends log output to the browser console. There are four logg
 
 ## Learn more
 
-Check out our [documentation](https://docs.launchdarkly.com) for in-depth instructions on configuring and using LaunchDarkly. You can also head straight to the [complete reference guide for this SDK](https://docs.launchdarkly.com/sdk/client-side/javascript). Additionally, the authoritative full description of all properties, types, and methods is the [online TypeScript documentation](https://launchdarkly.github.io/js-client-sdk/). If you are not using TypeScript, then the types are only for your information and are not enforced, although the properties and methods are still the same as described in the documentation.
+Read our [documentation](https://docs.launchdarkly.com) for in-depth instructions on configuring and using LaunchDarkly. You can also head straight to the [complete reference guide for this SDK](https://docs.launchdarkly.com/sdk/client-side/javascript). Additionally, the authoritative full description of all properties, types, and methods is the [online TypeScript documentation](https://launchdarkly.github.io/js-client-sdk/). If you are not using TypeScript, then the types are only for your information and are not enforced, although the properties and methods are still the same as described in the documentation.
 
 For examples of using the SDK in a simple JavaScript application, see [`hello-js`](https://github.com/launchdarkly/hello-js) and [`hello-bootstrap`](https://github.com/launchdarkly/hello-bootstrap).
 

example/index.html

@@ -228,7 +228,7 @@ <h4>
           <div class="card">
             <div class="card-body">
               <p>
-                These actions are for testing LaunchDarkly's analytics events and A/B testing features.
+                These actions are for testing LaunchDarkly's analytics events and Experimentation features.
               </p>
               <form class="form-inline mb-2">
                 <button id="pushUrlButton" class="btn btn-secondary btn-sm mr-2" type="button">

src/httpRequest.js

@@ -32,7 +32,11 @@ export default function newHttpRequest(method, url, headers, body, pageIsClosing
     }
   }
   if (pageIsClosing) {
-    xhr.send(body); // We specified synchronous mode when we called xhr.open
+    try {
+      xhr.send(body); // We specified synchronous mode when we called xhr.open
+    } catch (e) {
+      // do nothing intentionally to suppress noise for now
+    }
     return emptyResult; // Again, we never want a request to be retried in this case, so we must say it succeeded.
   } else {
     let cancelled;

typings.d.ts

@@ -65,10 +65,10 @@ declare module 'launchdarkly-js-client-sdk' {
     hash?: string;
 
     /**
-     * Whether the client should make a request to LaunchDarkly for A/B testing goals.
+     * Whether the client should make a request to LaunchDarkly for Experimentation metrics (goals).
      *
      * This is true by default, meaning that this request will be made on every page load.
-     * Set it to false if you are not using A/B testing and want to skip the request.
+     * Set it to false if you are not using Experimentation and want to skip the request.
      */
     fetchGoals?: boolean;
 
@@ -99,15 +99,15 @@ declare module 'launchdarkly-js-client-sdk' {
    */
   export interface LDClient extends LDClientBase {
     /**
-     * Allows you to wait until the client has received goals data from LaunchDarkly.
+     * Allows you to wait until the client has received metrics (goals) data from LaunchDarkly.
      *
-     * This is only relevant if you are using A/B testing features like click events and
-     * pageview events; until the client has received the configuration for these (which
-     * happens immediately after the initial request for feature flags), click events and
+     * This is only relevant if you are using Experimentation features like click events and
+     * pageview events. Until the client has received the configuration for these, which
+     * happens immediately after the initial request for feature flags, click events and
      * pageview events will not work, so you may wish to wait using this method before
      * doing anything that you expect to generate those events.
      *
-     * The returned Promise will be resolved once the client has received goals data. If
+     * The returned Promise will be resolved once the client has received metrics data. If
      * you prefer to use event handlers rather than Promises, you can listen on the client
      * for a `"goalsReady"` event instead.
      *