Angular VS lit

Angular Docs AI sources are angular.dev, Angular GitHub Discussions and Angular GitHub Issues.

With both the HTTP Resource (more on that later) and the HTTP Client, we need to build the HTTP Resource request. In the upcoming PR for HTTP Resource, Angular has separated types and exposed a new type called HttpResourceRequest. If this is unavailable at the time of reading, you can take the following interface, which is extracted from the PR:

The PR relevant to httpResource: https://github.com/angular/angular/pull/59876

Selectorless template parsing #60724

@Component({ selector: 'app-root', imports: [ HttpResourceBlobComponent, HttpResourceArrayBufferComponent, HttpResourceTextComponent ], templateUrl: './app.component.html', changeDetection: ChangeDetectionStrategy.OnPush, }) export class App { version = VERSION.full; prs = [ 'https://github.com/angular/angular/pull/59876', ]; name = 'httpResource sub-constructors'; description = 'httpResource functions to query non-JSON data'; }

components bindings

UmiJS is an [extremely] pluggable enterprise-scale React-based web application [meta]framework, offering (as many analogs) routing, build tools, dedicated design system, and everything in between. From what I could see during my reconnaissance, its main market is huge enterprise monorepos for React websites and web applications (something very opposite to tools like, for instance Waku, if you will). Umi itself is not exactly a metaframework though, as I'd say, but rather something React would be if it aimed to resemble Angular as of version 19 — the powerful SPA framework with optional support for SSR/SSG and a whole lot of build options making it very customizable and approachable for performance optimizations specific to each particular use case. Its plugins-driven extensibility is something resembling Vite but for a more dedicated goal of building rich user interfaces. And there's more.

For more information, check out the Angular async pipe implementation on GitHub.

The PR of the feature: https://github.com/angular/angular/pull/57051

some people cheat by using web components but with Lit Elements. https://lit.dev/

Lit[0] is the underdog winner here. Like the OP, I much prefer functional style and Lit is the only class-based thing in my repos, but it is much easier to deal with the lifecycle than React effects and hooks.

Lit is nearly bare metal HTML (and has been proposed as a permanent addition to standard HTML. It also doesn't need JSX because you just write regular HTML in tagged template literals.

Nearly all the "new, improved" reactive frameworks I see that are "better than React" are just trying to reinvent Lit.

[0] https://lit.dev

wtf are you taking about with “completely abandoned”? https://github.com/lit/lit/pulse/monthly

First I take a look at how other libraries/frameworks implement SSR and found out that they either simply don't implement DOM at all or implement the least of it (like Lit).

As HAX project lead, our platform works exclusively through the building and nesting of 1,000s of Web Components and most (~95%) use ShadowRoots via Lit / LitElement.

Lit

Lit lit.dev Fast, lightweight Web Component library.

My favourite Custom Elements Manifest generator is the one by open-wc. The setup is straightforward: you create a config file and tell it where to find your components. It even has support for Lit out of the box.

And it is built with https://lit.dev a fantastic library !

> since Material Web seemed to quickly end up in maintenance mode

This is really unfortunate to say the least - the engineering team has done a fantastic job there, but apparently no backing from Google despite the nice promise at the the launch of Material Web.

If you're looking for a library to build components and apps with that does let you use plain JavaScript - to the degree that you can write working components in your devtools console - check out Lit: https://lit.dev/

Lit's used by pretty major apps like Photoshop, Reddit, Home Assistant, and The Internet Archive.