Import of helpers from swagger-client worked because of the fact
that commonjs exports are basically an objects that can be destructured.
Whenever swagger-client switches to ES6 imports as primary mechanism
of webpack consuptions imports like that will fail. This change makes
sure that import mechanism is both compatible with ES6 and commonjs
import systems.

Along with that rename default import of swagger-client
to more appropriate SwaggerClient.

As resolving applies to everything and not just specific builds
the resolve.aliases have been moved to one common place.

As versions of libraries that are both used by swagger-js and swagger-ui
may diverge in time, we must use webpack resolve aliases to make sure
that only one version of these libraries gets bundled.

Avoid mapping Immutable.Map as React children.
Co-authored-by: NVladimir Gorej <vladimir.gorej@gmail.com>

Ref https://github.com/immutable-js/immutable-js/issues/667

Ref https://github.com/immutable-js/immutable-js/issues/667

Refs #6082

* use curlify flag isMultipartFormDataRequest
* curlify test updated
Co-authored-by: NVladimir Gorej <vladimir.gorej@gmail.com>

* directly load data:image/svg+xml
* current webpack config only allows inline file via jsx

On server-side execution `dompurify` exports factory function instead of
a purifier instance. Because of this, server-side code that imports
SwaggerUI (e.g. via `swagger-ui-react`) fails, since `DomPurify.addHook`
does not exist.

This affects universal rendering apps which share code
between client-side and server-side.

* Move next to download button and match styling
Co-authored-by: NAldrin Abastillas <AAbastillas@rcanalytics.com>
Co-authored-by: NTim Lai <timothy.lai@gmail.com>

* README updated
* renamed package.json to _sample_package.json
* removed package-lock.json

This commit changes markdown sanitization behaviour in following way:

class, style and data-* attributes are removed by default. These attributes
open possible vulnerability vectors to attackers.

The original behavior of sanitizer (before this commit) can be enabled by *useUnsafeMarkdown* configuration option.
Use this configuration option with caution and only in cases when you know
what you're doing.

* Replace Base64 encoded SVGs with unencoded version. Replace partially URL encoded SVGs with unencoded version, removing extraneous LF character