lit VS minze

Compare lit vs minze and see what are their differences.

lit

Lit is a simple library for building fast, lightweight web components. (by lit)
Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
lit minze
139 10
17,347 542
1.9% 0.4%
9.5 9.7
3 days ago about 2 months ago
TypeScript TypeScript
BSD 3-clause "New" or "Revised" License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

lit

Posts with mentions or reviews of lit. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-16.
  • Show HN: I made a Pinterest clone using SigLIP image embeddings
    2 projects | news.ycombinator.com | 16 Feb 2024
  • What We Need Instead of "Web Components"
    8 projects | news.ycombinator.com | 22 Dec 2023
    actually, looking at it (https://lit.dev/), i do exactly that.

    I also define a `render()` and extend my own parent, which does a `replaceChildren()` with the render. And, strangely, I also call the processor `html`

    I'll still stick with mine however, my 'framework' is half-page of code. I dislike dependencies greatly. I'd need to be saving thousand+ lines at least.

    Here, I don't want a build system to make a website; that's mad. So I don't want lit. I want the 5 lines it takes to invoke a dom parser, and the 5 lines it takes do define a webcomp parent.

  • Web Components Aren't Framework Components
    2 projects | news.ycombinator.com | 11 Dec 2023
    I rather like https://lit.dev/ for web components so far.

    For the reactivity stuff, you might want to read https://frontendmasters.com/blog/vanilla-javascript-reactivi... - it shows a bunch of no-library-required patterns that, while in a number of cases I'd much rather use a library myself, all seems at least -basically- reasonable to me and will probably be far more comprehensible to you than whatever I'd reach for, and frameworks are always much more pleasant to approach after you've already done a bunch of stuff by banging rocks together first.

  • Reddit just completed their migration out of React
    2 projects | /r/reactjs | 8 Dec 2023
  • Web Components Eliminate JavaScript Framework Lock-In
    10 projects | news.ycombinator.com | 27 Nov 2023
    I work on Lit, which I would hesitate to call a framework, but gives a framework-like DX for building web components, while trying to keep opinions to a minimum and lock-in as low as possible.

    It's got reactivity, declarative templates, great performance, SSR, TypeScript support, native CSS encapsulation, context, tasks, and more.

    It's used to build Material Design, settings and devtools UIs for Chrome, some UI for Firefox, Reddit, Photoshop Web...

    https://lit.dev if you're interested.

  • HTML Web Components
    14 projects | news.ycombinator.com | 13 Nov 2023
    I am more a fan of the augmented style because it doesn't entrap you in dev lock-in to platforms.

    The problem with frameworks, especially web frameworks, is they reimplement many items that are standard now (shadowdom, components, storage, templating, base libraries, class/async, network/realtime etc).

    If you like the component style of other frameworks but want to use Web Components, Google Lit is quite nice.

    Google Lit is like a combination of HTML Web Components and React/Vue style components. The great part is it is build on Web Components underneath.

    [1] https://lit.dev/

  • Web Components Will Outlive Your JavaScript Framework
    16 projects | news.ycombinator.com | 25 Oct 2023
    2. https://github.com/lit/lit/tree/main/packages/labs/router

    Both follow the mental model of mapping a URL pattern to a component fairly intuitively.

    16 projects | news.ycombinator.com | 25 Oct 2023
    > Finally, the last thing I would suggest is that writing an entire app in vanilla web components is kind of crazy talk in my opinion. For 5kb you can have a super nice developer experience using Lit (https://lit.dev)

    I 100% agree with this. For me it was more of a question of "can I do it", and that was something I wanted to find out. You notice that I ended up having to recreate a significant chunk of lit-like functionality on my own via a base class: https://github.com/jjcm/nonio-frontend/blob/master/component...

    I would very much recommend not going full vanilla. Using a library like lit will definitely help making things easier/more polished, and will integrate better with existing tooling.

    16 projects | news.ycombinator.com | 25 Oct 2023
    From the comments I see here, it seems like people expect the Webcomponents API to be a complete replacement for a JS framework. The thing is, our frameworks should start making use of modern web APIs, so the frameworks will have to do less themselves, so can be smaller. Lit [0] for example is doing this. Using Lit is very similar to using React. Some things work different, and you have to get used to some web component specific things, but once you get it, I think it's way more pleasant to work with than React. It feels more natural, native, less framework-specific.

    For state management, I created LitState [1], a tiny library (really only 258 lines), which integrates nicely with Lit, and which makes state management between multiple components very easy. It's much easier than the Redux/flux workflows found in React.

    So my experience with this is that it's much nicer to work with, and that the libraries are way smaller.

    [0] https://lit.dev/

    16 projects | news.ycombinator.com | 25 Oct 2023
    Regarding the point you mentioned about not being able to pass objects via attributes, you can however pass them via properties on the element.

    Also as for the state management side of things there is nothing at all stopping you from hooking up whatever state management solution you want. I’ve even seen a bunch of solutions that use the browsers built in event model as well if keeping dependencies to a minimum is your goal.

    Finally, the last thing I would suggest is that writing an entire app in vanilla web components is kind of crazy talk in my opinion. For 5kb you can have a super nice developer experience using Lit (https://lit.dev)

minze

Posts with mentions or reviews of minze. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-03-14.

What are some alternatives?

When comparing lit and minze you can also consider the following projects:

Svelte - Cybernetically enhanced web apps

stencil - A toolchain for building scalable, enterprise-ready component systems on top of TypeScript and Web Component standards. Stencil components can be distributed natively to React, Angular, Vue, and traditional web developers from a single, framework-agnostic codebase.

Vue.js - This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core

Angular - Deliver web apps with confidence 🚀

htmx - </> htmx - high power tools for HTML

Preact - ⚛️ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.

astro - The web framework for content-driven websites. ⭐️ Star to support our work!

vite - Next generation frontend tooling. It's fast!

uhtml - A micro HTML/SVG render

shoelace-css - A collection of professionally designed, every day UI components built on Web standards. Works with all frameworks as well as regular HTML/CSS/JS. 🥾

React - The library for web and native user interfaces.

storybook - Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.