Importing Swagger UI #2877
-
|
I have a custom component called <script>
import SwaggerUI from 'swagger-ui-dist/swagger-ui-bundle.js';
import 'swagger-ui-dist/swagger-ui.css';
export default {
name: 'SwaggerUI',
props: {
url: {
type: String,
required: true
},
isDark: {
type: Boolean,
default: false
}
},
data() {
return {
dark: "dark",
light: "light"
}
},
watch: {
isDark: function (val) {}
},
mounted() {
SwaggerUI({
dom_id: '#swagger-ui',
url: this.url,
presets: [
SwaggerUI.presets.apis,
SwaggerUI.SwaggerUIStandalonePreset
],
})
}
}
</script>It was working fine until I am able to start the dev server though. I tried adding the following vite configs: export default defineConfig({
// ...
vite: {
build: {
commonjsOptions: { transformMixedEsModules: true, include: [] },
},
optimizeDeps: {
disabled: false,
},
}
})But that didn't fix too. Any help is appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
Have you tried adding 'swagger-ui-dist/swagger-ui-bundle.js' to |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, that did not work |
Beta Was this translation helpful? Give feedback.
-
|
Some reports on Swagger's repo suggest using Node 20 works 👀 Can you try that once as well? I'll take a look otherwise. Seems like it tries to use browser only APIs in it's classes. Dynamic importing those packages inside onMounted should also work. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah you are right. It works fine on Node 20. Super weird. It should be OK to build Vitepress in Node 20? |
Beta Was this translation helpful? Give feedback.
-
|
Yeah vitepress fully supports v20. |
Beta Was this translation helpful? Give feedback.
Some reports on Swagger's repo suggest using Node 20 works 👀 Can you try that once as well? I'll take a look otherwise.
Seems like it tries to use browser only APIs in it's classes. Dynamic importing those packages inside onMounted should also work.