# Rendering 'TypeError' with theme components after update

**URL:** https://meta.discourse.org/t/rendering-typeerror-with-theme-components-after-update/381263
**Category:** Bug
**Created:** [September 2, 2025, 10:10am UTC](https://meta.discourse.org/t/rendering-typeerror-with-theme-components-after-update/381263 "2025-09-02T10:10:38Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [September 2, 2025, 12:28pm UTC](https://meta.discourse.org/t/rendering-typeerror-with-theme-components-after-update/381263/4 "2025-09-02T12:28:30Z")

</div>

This might help track it down:

> [@Cannot put the template in the desired outlet](https://meta.discourse.org/t/cannot-put-the-template-in-the-desired-outlet/330650/11):
>
> Thank you. This really helps with the developer experience. Which as we know has improved dramatically with.gjs over widgets. however There are lots of very odd errors you can get when using gjs components that do not make finding the issues very easy. For example, lets mess up the helper name: {{html\_safe this.bannerTextContent}} Leads to the classic: program.js:100 Uncaught (in promise) TypeError: Invalid value used as weak map key at WeakMap.set (\<anonymous\>) (this also happens…

Check the helpers!

---

_[View the full topic](https://meta.discourse.org/t/rendering-typeerror-with-theme-components-after-update/381263)._