Augustine Kim

Yup definitely agree that we should highlight easy options like that on getting started. The different ways to try things out are so numerous these days! Adding vite is on...

Ah.. thanks for the report. Looks like these might be caused by the export of the directive implementation classes, but since the classes themselves don't have jsdoc, they somehow go...

another related thread on discord: https://discord.com/channels/1012791295170859069/1166630986876997684/1166630986876997684

Also related discussion here: https://github.com/lit/lit.dev/issues/860

We actually now have `Control/Command + K` shortcut for search now, though nowhere that communicates it.

For the `lit` package, we also have the `inlineSources` option (https://www.typescriptlang.org/tsconfig/#inlineSources) set true and do not include our ts source files in the npm package, just the js, js.map, d.ts,...

Some ideas on what we could add: Discourage usage of a barrel file that's a single `index.js` exporting all the components. Instead of a single `"main"` in the `package.json`, utilize...

Forgot to add that open-wc also recommends adding the custom elements manifest to the exports. https://custom-elements-manifest.open-wc.org/blog/intro/#how-should-i-use-a-custom-elements-manifest

Nothing from the code here looks wrong with regards to the properties. If you're certain the property is set on the child component via inspecting with the browser dev tool,...

That all looks fine.. It really shouldn't make a difference but you might try doing a property binding in the parent's render ``.