MagLit VS lit

There are many services that offer such a functionality. Just search for "password protected link shortener". One example would be https://maglit.me/ by u/NayamAmarshe (I haven't tried it, I only read this post). However if you care for privacy (kind of the point of the whole post) and you have a web server you might want to selfhost the service (has a lot of other advantages as well, link all the easy to remember keywords are still available), which gives you even more options: like again MagLit or YOURLS with the Password Protection Plugin. (disclaimer: I am using a self hosted YOURLS instance myself, but have not used this plugin yet).

Star it on Github: https://github.com/NayamAmarshe/MagLit

Someone here posted https://maglit.me/, but people had mixed reactions to it (try to search here).

The 'live preview' can be turned on with yarn dev or npm run dev. I made https://maglit.me with next.js.

Source Code with Verifiable Builds: https://github.com/NayamAmarshe/MagLit

My go-to front end these days is Lit with web components, rollup, and web dev server.

So far I have found two suitable candidates. They are Astro and Lit. Which one of these would you choose? And are there any others you can recommend?

next, use some framework such as lit.dev or Svelte. you may argue “you don’t need it now,” but I guarantee you that if you actually want to reuse this, you will at some point need a framework, and there is no sane way to consume raw HTML/CSS/JS in a framework. picking something is better than nothing. so all your work would be wasted.

If you want to create WCs I’d recommend looking into libraries specifically made to author them (e.g Lit).

Recently, on the Enhance Discord, there was a question about how to use Lit web components in an Enhance application. Since Lit components extend standard web components, adding Lit to your Enhance app is easy.

> Bo idea why you put SSR and web components in the same sentence

A typical JS framework fence sitter would build SSR first applications and might likely think about using a light weight framework like Svelte for a client rendered 'feature (or) two' like I did.

> There are multiple documented downsides, including by Rich Harris, the author of Svelte

In link [2] of my parent comment I've mentioned those, I've no technical contention on his PoV but that 'Custom Element' feature is buggy, Is not made clear upfront and that there's no intention to fix it.

> As long as you pretend you need web components for SSR, no framework will be right for you, including web components themselves.

What about web components first framework like Lit[1]? I'm not stating it as a fact, But asking?

[1] https://lit.dev/