chore: regenerate package-lock.json (#8411)

package-lock.json was regenerated using Node@16.13.2
and npm@8.1.2. Along with that, these Node.js and npm
versions were set to .nvmrc file.

Given that the dependency tree now changed,
webpack config resolve aliases needed to be
amended to reflect the current dependency tree.

.nvmrc

@@ -1 +1 @@
-16.8
+16.13.2

docs/development/setting-up.md

@@ -5,10 +5,7 @@ Swagger UI includes a development server that provides hot module reloading and
 ### Prerequisites
 
 - git, any version
-
-SwaggerUI Node.js support closely follows [Node.js Release Statuses](https://nodejs.org/en/about/releases/)
-and is only expected to work on `Current`, `Active LTS` and `Maintanenace LTS` versions of Node.js.
-SwaggerUI may also work on `Pending` or `EOL` versions of Node.js, but it's not guaranteed.
+- **Node.js >=16.13.2** and **npm >=8.1.2** are the minimum required versions that this repo runs on, but we recommend using the latest version of Node.js@16
 
 ### Steps
 

docs/usage/installation.md

@@ -4,9 +4,11 @@
 
 ### NPM Registry
 
-We publish two modules to npm: **`swagger-ui`** and **`swagger-ui-dist`**.
+We publish three modules to npm: **`swagger-ui`**, **`swagger-ui-dist`** and **`swagger-ui-react`**.
 
-**`swagger-ui`** is meant for consumption by JavaScript web projects that include module bundlers, such as Webpack, Browserify, and Rollup. Its main file exports Swagger UI's main function, and the module also includes a namespaced stylesheet at `swagger-ui/dist/swagger-ui.css`. Here's an example:
+**`swagger-ui`** is meant for consumption by JavaScript web projects that include module bundlers,
+such as Webpack, Browserify, and Rollup. Its main file exports Swagger UI's main function,
+and the module also includes a namespaced stylesheet at `swagger-ui/dist/swagger-ui.css`. Here's an example:
 
 ```javascript
 import SwaggerUI from 'swagger-ui'