Andrey (azangru) wrote,

Google has finally become ready to promote its Lit ecosystem properly. I thought they were going to make their announcements at the coming Google IO; but, to my surprise, they preempted that by holding a virtual event today where they announced the release of the new major version of the library, with the updates that address most of the concerns that I had when I tried to use LitElement in anger for the first time.

- There is a way to separate component's state from component's properties. Apparently it existed even before this update; but the docs weren't very clear on that. The docs were rather niggardly in the information they supplied, I must say.
- There is a proposal for a browser api to encapsulate the declarations of custom elements within their hosts. Which is clumsier than what we get with frameworks, but at least makes web components more suitable for large codebases.
- There is a convenient way to share common functionality between components.
- There is support of server-side rendering.

All in all, pretty uplifting stuff. But of course I am now entrenched in React at work.


Recent Posts from This Journal

  • (no subject)

    Thought of this phrase today for some reason, then thought whether it exists in English (putting toothpaste back into the tube came to mind), then…

  • (no subject)

    I think many (perhaps most) people are totally fine with being a free-rider, a bludger, or a sponge (remember Trump who said that he pays little…

  • (no subject)

    Someone who self-identifies as a technical writer, among other things, begins her article How To Build An E-Commerce Site With Angular 11, Commerce…

  • Post a new comment


    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.