-
Currently, module-resolver only works for a CDN like unpkg or using alias. We should give the ability to resolve module named imports to the node_modules folder.
Example
```js
import { LitElemen…
-
:heavy_check_mark: i've found that the extension works great to bring syntax highlighting to my lit-html render blocks:
```js
render() {
return html`cool!`
}
```
:question: however i was s…
-
Does this tool already support `lit 2.x`?
If I run `wca analyze` on a project which uses new lit version and does the import statements like below, then it doesn't create the `custom-elements.json`…
-
## Bug report notice
**Before** you file a bug, make sure that you did not make a configuration mistake. The Swiss Army Knife in its current state does not yet have full configuration sanity checks!
…
-
## Type of Change
- [ ] New Feature Request
- [ ] Documentation / Website
- [x] Improvement / Suggestion
- [ ] Bug
- [ ] Other (please clarify below)
## Summary
Noticed in https://github.com/…
-
# Description
`*.d.ts` has wrong import .
Use the starter project and build
https://github.com/PolymerLabs/lit-element-starter-ts
2. See this output...
After build `my-element.d.ts` …
-
### Which package(s) are affected?
Lit Core (lit / lit-html / lit-element / reactive-element)
### Description
I have a scenario where I'm trying to cache something that is rendered based on a provi…
-
# 🙋 Feature Request
Add an optional key to the `repeat` directive, so that `repeat` can map a DOM node to a specific item when updating views. Similar to how React or Lit work. This would be benefi…
-
Hi,
This is a very edge case. I am mainly reporting it in the hope that it could possibly hide a bigger problem.
Basically, is the package name in package.json has the same name as the directory t…
-
# Description
I have a template, which uses repeat. Snapshot tests fail now.
Before updating to lit@2.0 snapshots looked as follows:
```