# Bundling deps with ember-browserify vs. ember-auto-import

**URL:** <https://discuss.emberjs.com/t/bundling-deps-with-ember-browserify-vs-ember-auto-import/16002>\
**Category:** Ember CLI\
**Created:** [January 13, 2019, 2:04am UTC](https://discuss.emberjs.com/t/bundling-deps-with-ember-browserify-vs-ember-auto-import/16002 "2019-01-13T02:04:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Scott\_Newcomer](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/scott_newcomer/32/13468_2.png) [@Scott\_Newcomer](https://discuss.emberjs.com/u/Scott_Newcomer)\
**Post date:** [January 13, 2019, 2:04am UTC](https://discuss.emberjs.com/t/bundling-deps-with-ember-browserify-vs-ember-auto-import/16002/1 "2019-01-13T02:04:04Z")

</div>

I am updating a large application with many third party dependencies to use `ember-auto-import`. After solving some smaller issues (“fs” imports and webpack), I am now running into modules that aren’t natively able to run in “isomorphic” environments. This is expected (as per how the 3rd party deps were written), but not an issues with `ember-browserify`. We have guards for FastBoot environments for certain execution paths.

Moving to `ember-auto-import` has cropped up quite a few server side rendering errors (e.g. document is not defined) coming from those 3rd party deps. For me to solve these issues, I need to understand the differences between the two packages and the differences they create when bundling up our apps.

Does anybody have a bit more clarity on why `ember-auto-import` might be causing these issues? Or perhaps have experienced similar situations?