Consider another ts-lit plugin

[mickaelistria]

Current typescript-lit-html-plugin seems not very well maintained with no release for a year. Some other TypeSCript plugins exist for that, such as ts-lit-plugin, and seem more maintained/up-to-date. Wild Web Developer should consider switching.

[vrubezhny]

Two years later...
The Microsoft's typescript-lit-html-plugin stays unchanged since November, 2018 - https://github.com/microsoft/typescript-lit-html-plugin/tags, having the only two not attended PRs created by dependabot,
However the ts-lit-plugin doesn't look like a proper replacement. It isn't updated since June, 2020 - https://github.com/runem/lit-analyzer/tags.
It brings 4 high severity vulnerabilities and some old dependencies that duplicate the existing ones like typescript@3.9.10, for example, when we're currently using typescript@4.8.4 (thus creating very long paths for command lines on Windows) .
So, it doesn't look like a usable replacement at the moment.

$ npm audit
# npm audit report

glob-parent  <5.1.2
Severity: high
glob-parent before 5.1.2 vulnerable to Regular Expression Denial of Service in enclosure regex - https://github.com/advisories/GHSA-ww39-953v-wcq6
fix available via `npm audit fix --force`
Will install ts-lit-plugin@1.0.5, which is a breaking change
node_modules/glob-parent
  fast-glob  <=2.2.7
  Depends on vulnerable versions of glob-parent
  node_modules/fast-glob
    lit-analyzer  0.0.7 - 1.2.1
    Depends on vulnerable versions of fast-glob
    node_modules/lit-analyzer
      ts-lit-plugin  >=1.0.6
      Depends on vulnerable versions of lit-analyzer
      node_modules/ts-lit-plugin

4 high severity vulnerabilities

[sebthom]

So, the situation doesn’t look much better as of today:

• For typescript-lit-html-plugin, the last npm release was published 7 years ago, and the most recent commit in the GitHub repository dates back 2 years.
• The ts-lit-plugin from the runem/lit-analyzer project was last published 2 years ago on npm.

There is also a fork of lit-analyzer/ts-lit-plugin that was quite active for about a year (GitHub), but it has few stars, hasn’t seen any commits in the past 3 months, and open issues are currently going unanswered.

Since the number of security and deprecation warnings is increasing I wonder if we should drop lit support all together?

[mickaelistria]

I don't know enough of the TS world to have any better proposal. I suspect that with typescript and typescript-languge-server themselves improving, lit have become less interesting and can be removed.
Usually, those lit can be enabled in project-specific settings; so if there is nothing that is beneficial for users in general, let's drop them all and just let users pick whatever lit they want in their project.