vite-imagetools VS MDsveX

The first thing is to install vite-imagetools from https://github.com/JonasKruckenberg/imagetools

Automatic image optimization via vite-imagetools.

The closest solution I’ve found is hacking something together yourself with vite-imagetools

The projects this solutions works with are customised Sveltekit projects I made. It has everything: markdown parser using Mdsvex, image converting tool using vite-imagetools, it has toml parser, and of course live preview and lots of other smaller things like markdown directives.

#2 - I'm not sure about the performance and/or resource usage implication around importing over 100 images like this. Would all of these images get bundled and included in the production build? The upside here is that something like vite-imagetools could be used if/when needed.

Hello HN,

I had some christmas free time over the last two weeks (Merry Christmas btw ;-)) and used that time to completely recreate the website of my app[1]. I used all the fancy new tools. I didn't know some of them when I started.

What was my goal?

* Pretty website

* Blazing fast

* Mobile first

* SSR

* Webp support

* Generally all the best website practices (high lighthouse score)

What did I use?

* Tailwindcss (https://tailwindcss.com/)

* Tailwind Components (https://tailwindui.com/)

* React (https://reactjs.org/)

* ViteJs (https://vitejs.dev/)

* Kubernetes (https://kubernetes.io/)

Well what can I say. I hate creating websites, but this was an awesome experience. Never have I created a website more efficiently. Tailwindcss + Components is just the best. ViteJS is so so so much easier to setup compared to webpack and has SSR support on top of it. React has been around somewhat longer and I did a lot of projects with it, so that was a nobrainer. Special thanks to all the people who created these awesome tools.

PS: If you work with lots of images, do yourself a favor and use something like https://github.com/JonasKruckenberg/imagetools. It saved me hours of dreadful work.

[1] https://stockevents.app

Spent the better part of today attempting to find a working alternative to svelte-images, which I had been using in Sapper, but found was not working in SvelteKit. Was referred to [vite-imagetools](https://github.com/JonasKruckenberg/vite-imagetools) on discord, which is a vite plugin that dynamically import and transform images (srcset). Here are the steps required to integrate vite-imagetools with SvelteKit:

In the ever-evolving world of web development, content remains king. For sites heavy with documentation, blogs, guides, changelogs, or engineering wikis, Markdown has emerged as the go-to language for crafting readable, maintainable content. However, the standard Markdown might not always fit the bill, especially when you're looking to add a unique touch or specific functionality to your Svelte-powered websites. Enter mdsvex - a Svelte preprocessor that not only understands Markdown but extends its capabilities, allowing developers to introduce custom-flavored Markdown.

I was working on my blog websites. The current method I use to add more posts is using mdsvex(https://github.com/pngwn/MDsveX) it turns my markdown files into post.

Oh right sorry. MDSVEX is a preprocessor for using Svelte components in markdown files. SVX is just the file format for it

If mdsvex is not applicable, I would still look through it's sources to see how they handle it and maybe find some useful ideas. Looks like there are multiple packages that handle all that parsing and preparing: https://github.com/pngwn/MDsveX/tree/master/packages

You can use those components in plain markdown. We will have to write documentation for inlang. Instead of requiring a preprocessor like MDX, MDsvex, or Stripe Markdoc, web components can be used instead. Reducing boilerplate, increasing maintainability and last but not least the community does not have to reinvent the wheel for every markdown preprocessor. Just use the platform. Just use web components in markdown.

SvelteKit plus mdsvex. There are quite a few examples out there, e.g. https://github.com/rodneylab/sveltekit-blog-mdx.

One issue we previously had with parsing Markdown with MDsveX was how to get a list of blogs without embedding all the blog content into some JS files... There's quite a few posts online and that's why I figured I'd talk about it here because it seems to be a common pain with SvelteKit and adapter-static. Ultimately what we did was use route parameters and different endpoints for the different requests, which you can see here.

We’re going to use mdsvex to render our Markdown posts. It’s a Markdown preprocessor for Svelte which allows you to use Svelte templating and components amongst your Markdown.