Augustine Kim

Could use https://www.npmjs.com/package/resolve.exports

I believe this is intentional to avoid TS users hitting errors like this https://github.com/lit/lit/issues/1780. TypeScript has yet to add support for trusted types: https://github.com/microsoft/TypeScript/issues/30024.

The problem is there are likely multiple versions of `@lit/reactive-element` installed which can be checked by `npm ls `@lit/reactive-element`. It's probably something like: ``` [email protected] └─┬ @lit/[email protected] └─┬ [email protected] └──...

I'm actually curious how others got to the point of seeing this error and what their `package.json` might look like? I can reproduce this error by installing a specific version...

Root cause of this error: `lit` package re-exports `LitElement` from the `lit-element` package which has its own dependency on `@lit/reactive-element` `lit` package re-exports all decorators from a direct dependency on...

Working as intended. See https://github.com/lit/lit/issues/3308#issuecomment-1275297241

> Would it make sense to add this API to the testing tool as a placeholder method? We could potentially add a no-op `.remove()` to the object returned by `.createElement()`...

I'll bring up adding a no-op `remove()` in the DOM shim to the team. For the CSS proposal, this one seems most relevant. https://github.com/WICG/webcomponents/issues/936

> I'll bring up adding a no-op `remove()` in the DOM shim to the team. So we are moving in a direction to reduce the reliance on these no-op DOM...

To clarify, the original post of the issue is more akin to issues like https://github.com/lit/lit/issues/1213 where bringing in the global DOM shim caused breakages. For purely importing Lit components in...