fix(webpack): enable SourceMaps in releases

[glowcloud]

Refs #9101

From the official Webpack documentation for devtool:

and guide for production:

Testing the options with the static HTML page in the dist folder:

• source-map (PR):

• nosources-source-map (current):

• hidden-source-map:

After building with the source-map option, the size of the dist folder went from 10 439 023 bytes (10,5 MB on disk) to 19 239 017 bytes (19,3 MB on disk)

[char0n]

TODO:

• we need to limit source map generation to certain build fragments (exports/browser only)
• we need to return sourceMap setting for Terser plugin
• we need to refactor the logic of determining if source map is to be generated
• we need to test on Safari
• ideally close all the source map related issues as resolved
• we always was source maps in dev environment because of direct chrome debugging capability
• ?? possibility to ignore vendor source maps ??

We decided that only certain build fragments that can/may be used in development env will contain source maps. Other will not as we're assuming nobody debugs in production and on production bundles (debugging in mostly done in development).

[glowcloud]

dist size after building: 11 804 809 bytes (11,9 MB on disk) with source maps included for core, es-bundle-core, dev and standalone.

Tested with a React application in Chrome:

Firefox:

and Safari:

[glowcloud]

There's also this line in es-bundle-core:

swagger-ui/webpack/es-bundle-core.js

Line 47 in b6805e5

devtool: sourcemaps && minimize ? "source-map" : false,

perhaps it was to bypass the previous nosources-source-map setting?

[char0n]

We don't want to generate source maps for standalone build UMD fragment because of:

We decided that only certain build fragments that can/may be used in development env will contain source maps. Other will not as we're assuming nobody debugs in production and on production bundles (debugging in mostly done in development).

[char0n]

There's also this line in es-bundle-core
perhaps it was to bypass the previous nosources-source-map setting?

We'll use new reusable helper for this one to align it with swagger-ui.js build fragment. This one always worked and generated properly working source map, but now we utilize some optimization on top of it.

[char0n]

Please also modify

swagger-ui/flavors/swagger-ui-react/release/run.sh

Line 12 in 955c0dd

cp ../../../dist/swagger-ui-es-bundle-core.js ../dist

[char0n]

Another references in

swagger-ui/.npmignore

Line 8 in 78f6ffb

!dist/swagger-ui-bundle.js