# New installs will default to Ember CLI builds in Production

**URL:** <https://meta.discourse.org/t/new-installs-will-default-to-ember-cli-builds-in-production/208282>\
**Category:** Announcements\
**Tags:** ember\
**Created:** [November 4, 2021, 6:49pm UTC](https://meta.discourse.org/t/new-installs-will-default-to-ember-cli-builds-in-production/208282 "2021-11-04T18:49:41Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [November 6, 2021, 8:21pm UTC](https://meta.discourse.org/t/new-installs-will-default-to-ember-cli-builds-in-production/208282/17 "2021-11-06T20:21:42Z")

</div>

> [@pfaffman](#):
>
> only theme components likely to be broken by this change are those Wyeth javascript in them?

That’s true - this ember CLI change doesn’t impact the HTML or CSS parts of themes/components.

In general, you can identify problem theme components by looking for yellow deprecation notices in the browser JS console under the old non-ember-cli environment. (Moving to Ember CLI is the reason we’ve been introducing these deprecations)

Meta has been running Ember CLI for a number of weeks now, and we’ve been working to make sure all our official themes/plugins are working in the new environment.

---

_[View the full topic](https://meta.discourse.org/t/new-installs-will-default-to-ember-cli-builds-in-production/208282)._