Vladimír Gorej

Created a [POC repo](https://github.com/char0n/swagger-ui-nextjs) integrating `swagger-ui-react@5` with `[email protected]`. Looks like Next.js now work with SwaggerUI without any configuration. This is probably related to https://github.com/swagger-api/swagger-ui/commit/6aa1b445b96cd9e26646b51ea99a54d86e6d59f1

Created a SwaggerUI wiki page https://github.com/swagger-api/swagger-ui/wiki/Seamless-Integration-with-Bundlers-&-Test-Tools where integration with Next.js is now documented.

Addressed by https://github.com/swagger-api/swagger-ui/pull/9111

Hi @ben12, This is actually already supported in SwaggerUI@5 and OpenAPI 3.1.0 definitions. ```yaml openapi: 3.1.0 info: title: Swagger Petstore description: 'This is a sample server Petstore server' version: 1.0.0...

> Thanks, it work. My mistake was the OpenApi version (3.0.3 instead of 3.1.0). I'm just glad that you can use this feature for your OpenAPI 3.1.0 definitions now. >...

Addressed by https://github.com/swagger-api/swagger-ui/pull/9435

We need to use https://www.npmjs.com/package/@svgr/webpack avoid the CSP issue.

Addressed the SVG assets in https://github.com/swagger-api/swagger-ui/pull/9209 There are additional tree SVG embedded in SASS files. These needs to be handled as well. - https://github.com/swagger-api/swagger-ui/blob/a43ae1c804b4ebc15bc7a39d27b068a60ea6a158/src/style/_form.scss#L10 - https://github.com/swagger-api/swagger-ui/blob/6ae2693d47397a919370eb19149f5514cb2f99f2/src/style/_models.scss#L50 - https://github.com/swagger-api/swagger-ui/blob/377b54a9987946121ec34e4be286cf027835824c/src/style/_buttons.scss#L191

Well with SVG assets embedded in CSS we have following options ### 1. extract as external SVG This is possible to do but the build will have to have additional...

All right, I've merged https://github.com/swagger-api/swagger-ui/pull/9209. It helps the situation a bit, but doesn't resolve the issue completely. We still need to resolve https://github.com/swagger-api/swagger-ui/issues/7540#issuecomment-1718984278