treshugart

3 ms·

1.
Use the Native Web Component Shadow DOM API as React Components(github.com)
12 points by treshugart 9y ago|1 comments
2.
Server-side rendering web components(medium.com)
2 points by treshugart 9y ago|0 comments
3.
by treshugart 10y ago
> I see you're already at v4 of the library, how often do you do breaking changes? It's partially a side-effect of following strict semver and using semantic-release but also that we intentionally favour breaking incrementally
4.
by treshugart 10y ago
Yeah, the comparisons need updating. I'd prefer not to have them because you're then subject to keeping your README up to date with everyone you compare to but some people have asked for them. I'm torn. That said, yes, Polyme
5.
by treshugart 10y ago
Disclaimer: I'm a contributor. First and foremost, Skate is a web component library designed to give you an augmentation of the specs focusing on a functional rendering pipeline and clean property / attribute semantics. It's
6.
by treshugart 10y ago
Thanks for the feedback :) Skate augments the web component spec and employs a functional rendering pipeline. Thus, your comment about it being "React in native web components" is a good elevator pitch, but we don't want to g
7.
by treshugart 10y ago
Someone has made this more idiomatic to the spec: https://github.com/tmpfs/trucks . FWIW, we are looking at decoupling Incremental DOM in a way where custom renderers can be created, so one could create a <template &
8.
SkateJS – A tiny, performant custom element library.(github.com)
1 points by treshugart 12y ago|0 comments