Build fragments a possible tree shaking

[char0n]

I've already documented current build fragments and how I foresee their future in this issue: #7831

I have problem using swagger-ui-es-bundle.js as it bundles the React with it. This build fragment is mapped in package.json in following way:

  "module": "dist/swagger-ui-es-bundle.js",

This means that when I use swagger-ui inside swagger-editor I end up bundling React twice which has side effects like these:

To translate this: When I want to use hooks, the app crashes as hooks as smart enough to realize the app is running two Reacts.

To fix that, me and I guess a lot of people as well need to use following webpack config:

      resolve: {
        alias: {
          "swagger-ui": path.resolve(projectBasePath, "node_modules", "swagger-ui", "dist", "swagger-ui-es-bundle-core.js"),
        },
      },

This works but the swagger-ui-es-bundle-core.js is commonjs bundle which pulls whole highlight.js and refractor libraries in. This issues about about creating remediation for swagger-ui-es-bundle-core.js build fragment and not to pull whole highlight.js and refractor libraries with it.