-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: run Slidev in browser #1800
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for slidev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
…nto feat/browserify
If the user can download an exported pdf version from the live version, this feature would be a killer feature for slidev. Together with #1972 would be huge. |
I tried out the PR and added some code on my local branch to test if you can add new slide with custom template other than default one, it looks something like this in packages/web/src/virtual/nav-controls.vue
However whenever a new slide is added, the layout being shown is still the layout of the last slide. When inspecting the value in devtools, the value of frontmatter is correct. Upon creating new slide, the layout is applied. But same issue happens again, so basically the frontmatter config is delayed by one slide. I don't know all the internals yet to find a fix so I'm writing here to report the bug. |
[WIP] This PR tries to run Slidev in the browser, with a better editor. I think the most commonly used functions work in the browser, but some don't. In this PR, changes to existing code will be very minimal, so the Node.js version will always be workable.
Although Slidev can run in StackBlitz, it is slow regarding startup time and operational efficiency.
Preview: https://deploy-preview-1800--slidev.netlify.app/web/