J

Use `svelte-add` (my tool): https://github.com/svelte-add/mdsvex

> I tried `setContext()` from the mdsvex layout and `getContext` in the default layout, but that didn't work because `__layout.svelte` runs first. Try making what's in context a store and...

I needed to solve the same problem today and I took a different approach by using `import.meta.glob` in a SvelteKit layout to import the page component given by the `path`...

This already works: ```svelte --- title: My lovely article author: Dr. Fabuloso the Fabulous coverimageAlt: Cool coverphoto --- import coverimage from "$assets/demopost/some-image.jpg" metadata.coverimage = coverimage; Blog post content ```

(Disclaimer: I didn't test this) I think you could write an mdsvex layout that [replaces the `pre` tag with a custom component](https://mdsvex.com/docs#custom-components). You can put a button that pulls the...

👋 We can't solve this problem because we're dependent on upstream https://github.com/sveltejs/eslint-plugin-svelte3/issues/10

~~Live reload possibly not working~~ Probably an upstream problem

> I manually added livereload: import livereload from "rollup-plugin-livereload"; to rollup.config and set it the config to dev && livereload("__sapper__/dev"), This allows the hot reload off of any rebuilds -...

Thanks for the report. I'm sorry this happened! It looks like Svelte Add's SvelteKit app initializer tried to run `npm install` for you after it had already successfully created the...

That will only happen during `dev`. It behaves correctly after a production build. Consider ignoring it. Yes, this is known and it's a Vite thing rather than a SvelteKit one,...