You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm trying to use iframes with relative src paths and was hoping that these would be handled in Slidev as they are in Vite (e.g. Vite serves the iframe sources and bundles scripts referenced in them).
Describe the solution you'd like
I was hoping it would be possible to have something like this in a slide:
<iframesrc="./example/basic.html"></iframe>
With that, I would like Vite to serve the ./example/basic.html in development and bundle referenced scripts when doing a build.
Describe alternatives you've considered
I have considered running a second instance of Vite to host the iframe sources during development and to generate the build after building with Slidev. This sounds very awkward.
The text was updated successfully, but these errors were encountered:
The workaround I am currently using is to add the iframe sources to the options.input (so these are included when building) and then to add middleware in configureServer that overrides response.end (to avoid the dev server behavior of using the same index.html for all *.html requests). Not feeling great about that, but it does seem to be working.
Is your feature request related to a problem? Please describe.
I'm trying to use
iframe
s with relativesrc
paths and was hoping that these would be handled in Slidev as they are in Vite (e.g. Vite serves the iframe sources and bundles scripts referenced in them).I see that Slidev allows assets like images and videos to be "imported" with relative paths.
Describe the solution you'd like
I was hoping it would be possible to have something like this in a slide:
With that, I would like Vite to serve the
./example/basic.html
in development and bundle referenced scripts when doing a build.Describe alternatives you've considered
I have considered running a second instance of Vite to host the iframe sources during development and to generate the build after building with Slidev. This sounds very awkward.
The text was updated successfully, but these errors were encountered: