How to use this with vite glob improt

[baseplate-admin]

Hi, it would be awesome if you showed an example on README.md on how to use svelte-retag with vite glob import.

---

coincidently, is it possible to migrate documentation to a domain? ( maybe with kit-docs )

[patricknelson]

Re: Glob import: Since that’s a Vite feature (not specific to svelte-retag), you can just infer it from here
https://vitejs.dev/guide/features#glob-import. I’m on the fence about going too far documenting that up front given I also have plans to eventually support <svelte:options …/> parsing so that would make that maybe a bit redundant, see: #44.

IMHO @baseplate-admin this isn’t documentation issue per se; it’s kind of a hack still. The core issue right now with auto-defining all your components this way is that you’re still importing every single component on every single page (even if it is clode-split), unless you break up your entry points to make sense with whatever page you’re on. So there’s still lots of manual effort. So I think what we really need is this: #32

For now though, if anyone stumbles upon this looking for a way to auto-define their components (and are cool with figuring out and are aware of the caveats noted above (please read through the tradeoffs listed in #32) then please see point 4 at #33 (comment) and notably the example code https://github.com/patricknelson/svelte-retag/blob/main/demo/vercel/src/main.js#L39-L88 which is not complete and possibly buggy (you’ve been warned).

So: Probably best to keep the official/outward documentation for svelte-retag minimal for now, at least for that specific capability. Especially once we figure out how #32 and #44 will work together. There will most likely be a flag somewhere where you simply set lazy: true so that it will just dynamically import() when a tag handled by svelte-retag is seen on the page and kicks into action. Combine that with SSR (or maybe even SWSR or via Cloudflare workers) + some hydration and then we’ll have a good solution that both SSR’s and hopefully performs well on core web vitals… even if you’re back-end is Python or PHP. 😎 Someday.

Re: Documentation: Maybe, that’ll take time. One person effort right now and I’m focused on core features necessary to help me build out my own project at the moment. Somebody has to work to build and maintain it and I don’t have time right now.