1. 1

    heh, it’s interesting that this Nutmeg thing advertises itself as “vanilla Web Components”, but it brings in lit-html as a dependency (and webpack + typescript stuff for dev dependencies). At this point, why not use lit-element? :)

    1. 3

      I initially built Nutmeg before LitElement was announced. Some of their patterns are pretty similar but Nutmeg doesn’t hide any of the native custom element APIs. If you look at the LitElement example in their readme they only mention customElements.define while Nutmeg surfaces connectedCallback, disconnectedCallback, observedAttributes, and attributeChangedCallback.

      The reality of it is you can’t write web code without a compilation step these days. Nutmeg also does a lot of best practice stuff so users don’t have to. Generating CI configs, default open source license, Renovate bot config, etc.

      1. 1

        you can’t write web code without a compilation step these days

        Well… yeah, unfortunately, there’s the issue with import paths. But if you don’t count a regex based path replacing server as a compiler, I’m doing it with no compilation in development :)

        1. 3

          Ship probably would have been a better word than write. Although I don’t want to write plain JS instead of TypeScript anymore.