# Alteração futura em componentes de tema 'use strict' - temas quebram após atualizar o Discourse

**URL:** https://meta.discourse.org/t/upcoming-theme-components-use-strict-change-themes-break-after-upgrading-discourse/185870
**Category:** Support
**Created:** [Abril 7, 2021, 12:20pm UTC](https://meta.discourse.org/t/upcoming-theme-components-use-strict-change-themes-break-after-upgrading-discourse/185870 "2021-04-07T12:20:59Z")
**Posts on this page:** 1
**Showing post:** 19

<div class="post-metadata">

### Author: ![Osama](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/osama/32/98013_2.png) [@Osama](https://meta.discourse.org/u/Osama)
#### Post date: [Abril 13, 2021, 9:48am UTC](https://meta.discourse.org/t/upcoming-theme-components-use-strict-change-themes-break-after-upgrading-discourse/185870/19 "2021-04-13T09:48:41Z")

</div>

Continuado aqui:

> [@Upcoming core changes that may break some themes/components (April 12)](https://meta.discourse.org/t/upcoming-core-changes-that-may-break-some-themes-components-april-12/186252?u=osama):
>
> Next week I’m going to merge [this PR](https://github.com/discourse/discourse/pull/12661) that allows themes and components to have QUnit tests, but it also changes how themes JavaScript is processed/transpiled by Discourse. Making those changes in a backward-compatible manner is very difficult without reworking lots of code in core (which may very well introduce other backward-incompatible changes), so the changes may break the JavaScript of your themes/components when you upgrade your site. In this post I’m going to explain what the changes are…

---

_[View the full topic](https://meta.discourse.org/t/upcoming-theme-components-use-strict-change-themes-break-after-upgrading-discourse/185870)._