# Erro do Uglifier durante a pré-compilação de assets

**URL:** <https://meta.discourse.org/t/uglifier-error-during-assets-precompile/96970>\
**Category:** Product Support\
**Tags:** unsupported-install\
**Created:** [11 Setembro , 2018 17:55 UTC](https://meta.discourse.org/t/uglifier-error-during-assets-precompile/96970 "2018-09-11T17:55:20Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![pjdc](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@pjdc](https://meta.discourse.org/u/pjdc)\
**Post date:** [24 Janeiro , 2019 03:03 UTC](https://meta.discourse.org/t/uglifier-error-during-assets-precompile/96970/7 "2019-01-24T03:03:58Z")

</div>

I ran into this myself recently on a different platform and solved it in a similar manner to OP.  
Although uglify-js is itself a node module, the uglifier gem bundles the code itself and executes it directly with ExecJS.  
However (see lib/tasks/assets.rake) the gem is only used if the node version is not available (or if it’s disabled).  
So the version of uglifier specified in Gemfile.lock is simply incompatible with some of discourse’s JS, unless harmony mode is used. This is probably worth fixing or else removing entirely.  
In any case, I now see that the expected situation is to install node and uglify-js so that Discourse uses that.

---

_[View the full topic](https://meta.discourse.org/t/uglifier-error-during-assets-precompile/96970)._