Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ES bundle uses CommonJS-style exports.

See original GitHub issue

Q&A (please complete the following information)

Swagger-UI version: 3.37.2
Swagger/OpenAPI version: N/A

Content & configuration

Apologies if this isn’t considered a bug, but I couldn’t find anything clearly explaining this. The ES bundle artefacts still use CommonJ-style exports. I expected that they would be utilising ES6/ES2015-style exports, for use in frameworks like Angular and others that prefer the ES format over CommonJS, for tree-shaking purposes.

swagger-ui-es-bundle.js: module.exports=function(e){var t={};function...

Should be something like: export default function(e){var t={};function...

Example Swagger/OpenAPI definition: N/A

Swagger-UI configuration options: N/A

Describe the bug you’re encountering

To reproduce…

Have a look at swagger-ui-es-bundle.js

Expected behavior

ES module should use ES-style exports.

Screenshots

N/A

Additional context or thoughts

Issue Analytics

State:
Created 3 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

andy-hancommented, Jun 16, 2022

Hello, is there any update to this? My organization has pretty strict compliance with our angular app, and this issue is preventing us from using this package.

0reactions

TimUnderhaycommented, Feb 19, 2021

@linelson as a temporary workaround, I’ve published a version with a corrected ES bundle. I intend to unpublish as soon as this is issue has been fixed, but should you wish to use it, it’s @kensingtontech/swagger-ui. I see that there is a PR in progress @ https://github.com/swagger-api/swagger-ui/pull/6720 so hopefully it won’t be too much longer.