Use the lit-element package instead of @polymer/lit-element

[justinfagnani]

Before the release of LitElement 1.0 we switched the package name from @polymer/lit-element to just lit-element. @polymer/lit-element is very, very old and unmaintained. lit-element has the current API and many bug and performance improvements.

[lemoustachiste]

Hi @justinfagnani and thank you for reaching out and letting us know.

Unfortunately we are stuck on the version of lit-element that is used. Indeed at the time we wrote the component, the lit-element was working in a certain way with redux (as per docs and examples) and we followed that and more. The version next version of the package we use actually breaks everything in the component and we haven't had, and probably won't have in the foreseeable future, time to refactor (rewrite?) everything.

[justinfagnani]

For Redux, I think the main thing you need to do is change this._requestUpdate() to this.requestUpdate() here:

blockcerts-verifier/src/store/connector.js

Line 33 in 585fa73

this._requestRender();

The basic mechanics of the LitElement lifecycle didn't change much, just some of the API names. _render() is now render(). Uses of _propertiesChanged could be changed to update() or updated(), but I think you should just be able to get rid of the this._props pattern completely, and instead of doing things like this._props.onClose() just do this.onClose() instead. The props passed to _propertiesChanged() are all instance properties, you really shouldn't need that bag separately.

The last time @polymer/lit-element was released was a year ago. It's quite behind at this point.