6 Commits (efd64d8a7ba6dae23abb32c03b40d4a6b0b249d4)

Author	SHA1	Message	Date
Divyansh Singh	d3b2957db0	fix: serialize config functions as code, not strings revived via new Function (close #3685) ... Functions in the site config (e.g. a custom miniSearch tokenize) were embedded in the client's JSON payload as source strings and rebuilt at runtime with new Function, which strict CSP blocks unless unsafe-eval is allowed. Emit them as plain function expressions in the generated script instead, with only an index marker left in the JSON, so the deserializer just looks them up. This also stops data strings that merely start with "_vp-fn_" from being evaluated as code. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	3 weeks ago
Divyansh Singh	5a368d3198	chore: format codebase and remove unused icons	4 weeks ago
Divyansh Singh	0e50d756f5	feat(markdown)!: rewrite include processing as a markdown plugin ... Moves <!-- @include: --> expansion out of markdownToVue and the local search plugin into an include plugin registered on the renderer, which wraps renderAsync and expands includes whenever the env carries a file path. createMarkdownRenderer users and createContentLoader with render or excerpt enabled now get includes expanded too (previously the directives silently came through unexpanded), and the expansion is reachable from the public API without exporting the helper (#4838). Region selection uses the region engine (all same-named regions concatenate, matched across comment styles), frontmatter of markdown files is stripped before locating regions and headings so both share one coordinate space, and the region suffix is anchored to the end of the include path, so paths containing # now work. Files reached by a failed render are still reported, so that creating a missing snippet or include recovers the page instead of requiring an edit of the including file. BREAKING CHANGES: - a missing region or heading anchor now throws instead of silently including the whole file, and out-of-bounds or inverted ranges throw instead of clamping; markdown.include.silent logs a warning and expands to nothing instead - markdown.include is a new option; false disables include processing - custom search _render functions receive the raw source (sync md.render does not expand includes; use renderAsync) - the include-expanded source is exposed as env.src Co-authored-by: Miroma <its.miroma@proton.me> Co-authored-by: Naloam <110604855+Naloam@users.noreply.github.com> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 months ago
Divyansh Singh	6a4a977ce5	refactor(node): normalize line endings at the file read boundary ... Adds readTextFile/readTextFileSync (CRLF/CR -> LF) next to the raw retrying readFile and switches the markdown-source readers to them (content loader, dynamic route templates, local search, includes). Raw reads stay in place where bytes must be preserved (serve, init scaffolding). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 months ago
Divyansh Singh	3372516152	fix(markdown): skip circular includes ... Expanding an include that is its own ancestor recursed forever. Track the ancestor chain and leave such includes unexpanded; the same file can still be included repeatedly as a sibling. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2 months ago
Divyansh Singh	a62ea6a832	feat: dynamic routes plugin overhaul (#4525) ... BREAKING CHANGES: Internals are modified a bit to better support vite 6 and handle HMR more correctly. For most users this won't need any change on their side.	2 years ago