nanocomponent
nanocomponent copied to clipboard
choojs
🚃 - create performant HTML components
`nanohtml` now supports document fragments, which are very handy for returning a collection of siblings without having to wrap them in an arbitrary element. However `nanocomponent` is not currently designed...
`this.element` is only briefly mentioned in docs, but is a pretty handy and key piece of the nanocomponent API. Would be good to document for users.
Not sure if we want this issue here or in [nanomorph](https://github.com/choojs/nanomorph), but looks like proxy nodes are leaked when a component is morphed to a new location in the dom....
Hi :wave: I have a situation where I have many components and some external libraries which manipulates the DOM. So, those libraries transform the root node of my components, and...
I was playing around with `nanocomponent` and `component-box` as possible target solution for jsx compilation and stumbled upon an issue. Sometimes we may expect updaing a component state by calling...
https://twitter.com/mattdesl/status/956940170468691968 It would be interested for comparisons sake to implement the example that @mattdesl does with preact in the above tweet.
I don't know of a good way to protect private vars from being overwritten. I know @toddself accidentally ran into the situation where he overwrote a private var. Perhaps we...
Apologies for the rough draft here; I didn't have much time to phrase things here properly, but I hope the general idea makes sense. This is mostly so we can...
In order to mount in iframes, we need to dynamically figure out the correct `document` https://github.com/choojs/nanocomponent/blob/master/index.js#L32
Maybe add the release process to CONTRIBUTING ``` Update changelog date Bump package.json commit -m '6.4.0' git tag v6.4.0 git push ; git push --tags npx gh-release npm publish ```