-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
resolve vite.config.ts
in parent directory
#1787
Comments
Sorry, I can't see the content of your |
Weird, it works for me Here is the content import MarkdownItSup from 'markdown-it-sup'
import { defineConfig } from 'vite'
export default defineConfig({
slidev: {
markdown: {
markdownItSetup(md) {
md.use(MarkdownItSup)
},
},
},
}) |
It seems that the |
vite.config.ts
in parent directory
It used to work in 0.49.10 and below I imagine that 0.49.11 introduces a behavior change Thanks, i did a symlink in the subfolders this fix the issue |
Hi,
Describe the bug
Markdown-it plugin seems to not work when the
slides.md
file is in a subfolderMinimal reproduction
Steps to reproduce the behavior:
I did a minimal reproductible test repository https://gitlab.com/pinage404/slidev_bad_subfolder_behavior/-/commits/main/?ref_type=HEADS
having the
slides.md
file in a subfolderwith this content in the
slides.md
add markdown-it plugin
With [email protected], plugin works
With [email protected], the build works but the plugin seems ignored
With [email protected] (current latest), same behavior as 0.49.11
Alternative solution
Moving the
slides.md
in the root folder fix itAdditional context
I noticed the backward incompatibility on this slide (the corresponding code)
Environment
If you are using Slidev globally (i.e.npx slidev
ornpm i -g slidev
), please try to reproduce the issue in a local project (i.e.npm create slidev@latest
).It was really long and hard to isolate the problem, good luck with this one
The text was updated successfully, but these errors were encountered: