Thank you for this, was looking for something like this!
Stencil – A reusable web component generator
91–100 of 107 posts
Re: Stencil – A reusable web component generator
#92Hey all, founder of Ionic (team behind Stencil) here. Didn't expect to see this up on HN so soon (released this morning), thanks for understanding there's still rough edges with docs, etc We built Stencil for a selfish reason: we needed more mobile web performance for Ionic apps being deployed as PWAs (in addition to App Store apps) and we were struggling getting that with traditional framework component/bundle appro…
Awesome work Max and team!
Thanks Dan! :D
Re: Stencil – A reusable web component generator
#93Hey all, founder of Ionic (team behind Stencil) here. Didn't expect to see this up on HN so soon (released this morning), thanks for understanding there's still rough edges with docs, etc We built Stencil for a selfish reason: we needed more mobile web performance for Ionic apps being deployed as PWAs (in addition to App Store apps) and we were struggling getting that with traditional framework component/bundle appro…
The main selling point of web components is that they are built using platform features and so they should be compatible with each other.
So in theory I should be able to mix and match web-components that are built using stencil, skatejs, polymer, or any other future opinionated web component library.
So is this also possible in practice and specifically can I mix stencil generated components with polymer ones (say use a paper-button inside a stencil compoenent) ?
Re: Stencil – A reusable web component generator
#94As kind of an old dog, I can't help but think of Active X controls from back in the day. That's what this reminds me of. Kinda.
Are there some guidelines and standardization of the kinds of events components emit, and what data is passed with the event? So that I don't have to look up all the variants of event names and data.
Re: Stencil – A reusable web component generator
#95I'm not sure I'm understanding the point behind this. If the main point is to allow people to reuse components (i.e. a calendar widget) across frameworks, then good, but it's going to be quite messy when things start to get complicated and we start hitting integration problems, because some guy on the Internet writing a widget is not going to test & maintain it on all frameworks. It also bothers me the whole Typescri…
Here an engineer at Ionic. You don't need to integrate typescript to use a "widget" generated with Stencil. Stencil is a compiler that generates vanilla web components in javascript. You can just import the generated .js and use the component just like a "button" or native "input".
I think you should consider disassociating the TypeScript requirement in the compiler. You'll alienate developers (like me) who prefer Vanilla™ JavaScript. It's one of the things I love about Svelte (which you claim heritage to), in that they really try to conform to vanilla everything, i.e., HTML, CSS, JS.
Everything else sounds terrific, though, especially the ability to do SSR.
Re: Stencil – A reusable web component generator
#96Fact: The website linked in this HN (stenciljs.com) was itself created with stencil. I encourage you guys to open the Dev Tools and dig into it!
nice diamond emoji
Re: Stencil – A reusable web component generator
#97I see two problems with stenciljs at the moment, but perhaps they can be fixed? 1, going back and forth in browser history, there is a flash of the footer being displayed before the actual content is loaded - it's just 1-2 frames, but very noticeable and disturbing. 2, scroll position is lost when visiting another page and going back.
Those are typical single page app problems, but they will probably not matter when using the framework for a hybrid app (no back button). If I'm to use this for a web app though, those would be nice to have addressed.
Re: Stencil – A reusable web component generator
#98Earlier quoted context omitted.
Hello all! We just deployed a new version of the site that should solve some of these problems, thanks for the feedback.
The font is still pretty tough to read on Windows/Firefox. It would be way more legible with a 400 font-weight.
Hey! Just wanted to mention that i pushed a deploy a few hours ago that changed it to a 400 font-weight.
Re: Stencil – A reusable web component generator
#99Hey all, founder of Ionic (team behind Stencil) here. Didn't expect to see this up on HN so soon (released this morning), thanks for understanding there's still rough edges with docs, etc We built Stencil for a selfish reason: we needed more mobile web performance for Ionic apps being deployed as PWAs (in addition to App Store apps) and we were struggling getting that with traditional framework component/bundle appro…
The main selling point of web components is that they are built using platform features and so they should be compatible with each other. So in theory I should be able to mix and match web-components that are built using stencil, skatejs, polymer, or any other future opinionated web component library. So is this also possible in practice and specifically can I mix stencil generated components with polymer ones (say u…
Yeah, as long as you have the polymer as dependency - it should work, you can mix it with vuejs, preact or angular 2+ already.
Re: Stencil – A reusable web component generator
#100Earlier quoted context omitted.
Ah good catch. It's MIT (will get that up soon)
Have you considered a BSD + PATENTS license? :P
Nothing wrong with that. In fact google releases quite a few projects like that - the important thing is what is inside the patents clause. Apache 2.0 also has one and no one argues against it.