Replies: 2 comments 2 replies
-
|
I love this idea! I just wanted to suggest it too. This way we could integrate more components inside too / use it inside a web app. Did you do any prior work? Is there a poc I can play with? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey!
I stared working on a vite plugin to run slidev during a vite dev/build in any existing codebase, in my case an astro-based website. I know that slidev already has an internal vite plugin, but it doesn't allow me to configure the build like I want it to. I want to be able to set the output path, control assets better, setup a glob pattern to find the files to export etc. It should then allow me to build my website with vite, but also generate the slides with the same vite process.
Due to the limited exports of
@slidev/cli, this ended up being a bit tricky. This has several reasons, but the main issues are that slidev commands likebuildandexportSlidesare not exported from the CLI package. You could export them from the direct path, likeimport { exportSlides } from "@slidev/cli/dist/export-D1Zqc-n1.js";, but I don't have to tell you that this is not a nice idea xDI would love to either
vite-plugin-slidev), orstandaloneentrypoint for slidev, not as a way to configure the CLII already have a POC plugin working, so if this idea sounds right to you, I can open a example PR to include a plugin as a sub-package in this repo.
What do you think? Or, did I overlook some option to do what I want with the existing vite plugin?
Cheers!
Beta Was this translation helpful? Give feedback.
All reactions