# Update react component without re-rendering entire element

**URL:** <https://talk.observablehq.com/t/update-react-component-without-re-rendering-entire-element/1106>\
**Category:** Help\
**Created:** [August 17, 2018, 6:33pm UTC](https://talk.observablehq.com/t/update-react-component-without-re-rendering-entire-element/1106 "2018-08-17T18:33:46Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![bgchen](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/bgchen/32/784_2.png) [@bgchen](https://talk.observablehq.com/u/bgchen)\
**Post date:** [September 6, 2018, 1:48am UTC](https://talk.observablehq.com/t/update-react-component-without-re-rendering-entire-element/1106/15 "2018-09-06T01:48:31Z")

</div>

Yeah, unfortunately, issues with unpkg (which `require` uses by default), wzrd.in, and bundle.run are all too frequent. There’s another thread about them [here](https://talk.observablehq.com/t/bundle-run-errors-breaking-notebooks/1050), with no solution, sadly.

---

_[View the full topic](https://talk.observablehq.com/t/update-react-component-without-re-rendering-entire-element/1106)._
