Rune Mehlsen

@abdonrd Unfortunately I've had some problems with my hands (it's slowly getting better), so I had to pause OSS development in the meantime. The Lit team has been really kind to offer their help on preparing lit-analyzer for the next version of Lit, so you can expect some updates soon 🙂

@RuneMehlsen is lit-analyzer still in development? No movement has been seen for a long time. github.com/runem/lit-anal…

@marcushellberg @gitpod Thanks for making me aware of this! I've now signed the agreement, and it should be available on Open VSX again 🙂

@RuneMehlsen, any chance you could add lit-plugin to Open VSX to make it available in @gitpod and other VS Code compatible editors? Looks like you need to agree to a new publisher agreement github.com/runem/lit-anal… Once you've used lit-plugin, there's no going back 🙂

@justinfagnani Thank you so much! I've been working on this update for quite some time now, and I'm so excited to finally release it 😃

📰 Version 1.2.0 of lit-analyzer is out with up to 15x faster type checking!!! 🏎 Really amazing work by @RuneMehlsen 🤩 github.com/runem/lit-anal… npmjs.com/package/lit-an…

@btopro I haven't yet finished the work on upgrading web-component-analyzer to v1.0.0 for this plugin, but you can follow the work in this issue :-) github.com/runem/lit-anal…

@RuneMehlsen is there something that needs updated now that things are at 1.0.0 for VSCode to work? Followed the docs and updated the internal variable to find all my files but not autocompleting tags :(

📣 Announcing <api-viewer> element 0.1.0 📖 UI for web-component-analyzer by @RuneMehlsen 🖋 Document your custom elements API ⚙️ Properties, attributes, events, slots 🛠️ Supports markdown in JSDoc comments github.com/web-padawan/ap…

@kennethrohde @justinfagnani @rictic @momondo My excitement already started at Polymer Summit 2017 where lit-html was announced 🎉 But your talks definitely also takes part in it! Please do more of them 🙌

@justinfagnani @RuneMehlsen @rictic I believe that the first time I met Rune was when I gave a talk about lit at @momondo - if that helped making him excited about lit, now seeing the result, I should do more such talks 😁

Want to typecheck and lint LitElement and lit-html templates in your build/test system? Now you can: npx lit-analyzer {src} --strict

@justinfagnani @PowersBenny Yes it does :-)

@PowersBenny Don't know. @RuneMehlsen ?

@kennethrohde @daKmoR @code web-component-analyser is generic and focused on analyzing attrs,props,events,eg on Web Components built with any library but isn’t focus on how it’s rendered. The lit CLI would include all that and then also analyze the html as well. Im open for just having one single CLI tho :)

@RuneMehlsen @daKmoR @code Why not lit+generic ... Seems good to always support generic

A new version of lit-plugin for @code is out now 🎉 ⚡️ Autocompletion for attributes, properties, events and slots 💅 CSS support out of the box 🔥 Improved web component analyzer 📝 Supports vscode custom html data format marketplace.visualstudio.com/items?itemName…

@adamdbradley @kennethrohde @daKmoR @code Right now the library analyzes the typings outputted by stencil. This makes it possible to provide an excellent IDE experience for using web components made with stencil :-)

@kennethrohde @RuneMehlsen @daKmoR @code Yes stencil is auto generating web-components.json: @ionic/core@4.2.0/dist/web-components.json" target="_blank" rel="nofollow noopener">unpkg.com/@ionic/core@4.… Is that what you mean? It also generates types for just static HTML and types for JSX.

@daKmoR @code I actually built a general web component analyzer that provides linting and documentation generation for web components and I’m planning on extracting lit-plugin functionality into a lit specific CLI: github.com/runem/web-comp…

@RuneMehlsen @code That looks really nice :) did you had any contact with the vs code team itself? they are also interested in providing it: github.com/w3c/webcompone… moreover, it would be awesome to converge on an analyzer to build tools on top of it like html linting and documentation generation

@daKmoR @code Thanks! :-) I have been following that thread closely which resulted in the custom html data format as of now. I will work on supporting formats that we agree on in the community.

@justinfagnani @kennethrohde @code I agree! I added the list because people were confused of the difference. The lit-html vscode plugin is a great plugin and I’m also describing its strengths in the section before the comparison list :-)

@kennethrohde @RuneMehlsen @code Nice feature list. I'd rather see convergence than competition here though.

@abdonrd @justinfagnani @code I'm happy that you like it! :-)

@RuneMehlsen @justinfagnani @code Thanks Rune! 👏

@justinfagnani @lastmjs @kennethrohde Indeed! I just updated my issue to include this point :-) github.com/runem/ts-lit-p…

@RuneMehlsen @lastmjs @kennethrohde It really should allow any properties. You don't have to declare a property to set it. You can set .id, .className, inherited from HTMLElement too.

I just published "lit-plugin": a vscode plugin that adds type checking, code completion and highlighting for lit-html. It automatically finds web components in your code and libraries! Please give it a try and tell me what you think :-) marketplace.visualstudio.com/items?itemName…

@lastmjs @kennethrohde I have also opened an issue regarding making it possible for lit-plugin to find tag names based on custom functions as expanding HTMLElementTagNameMap can be a bit cumbersome. github.com/runem/ts-lit-p…

@RuneMehlsen @kennethrohde As a separate concern, I'll be using my own customElement function to define my custom elements. What would it take to support this? github.com/lastmjs/functi…

@lastmjs @kennethrohde Regarding lit-plugin not finding props on custom elements please see the issue I just created on the repository: github.com/runem/ts-lit-p… As for using your own custom element function I recommend that you expand the HTMLElementTagNameMap TS interface (see example in the readme)

@lastmjs @kennethrohde How did you define the property? Right now it only looks at properties with the lit-element property-decorator and not general public fields on the class. Ill take a look at improving it this weekend :-)

@RuneMehlsen @kennethrohde Alright, I'm trying it out. It's giving me an unknown attribute error when I'm trying to set a property on one of my custom elements...I have the property defined with TypeScript in my custom element

@KnottTsavo Thanks a lot! I’m happy that you like it 🎉

@RuneMehlsen This is so sick ! Thanks my dude !