# Debugging Ember Cli

**URL:** <https://discuss.emberjs.com/t/debugging-ember-cli/6379>\
**Category:** Uncategorized\
**Created:** [September 29, 2014, 11:39pm UTC](https://discuss.emberjs.com/t/debugging-ember-cli/6379 "2014-09-29T23:39:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![emorling](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/emorling/32/9484_2.png) [@emorling](https://discuss.emberjs.com/u/emorling)\
**Post date:** [September 29, 2014, 11:39pm UTC](https://discuss.emberjs.com/t/debugging-ember-cli/6379/1 "2014-09-29T23:39:23Z")

</div>

1. Is it possible to effectively debug Ember-Cli?
2. All javascripts are being compiled into vendor.js in the development environment, is it possible to turn this off?
3. In the browser I get “[http://0.0.0.0:4200/assets/jquery.min.map](http://0.0.0.0:4200/assets/jquery.min.map) 404 (Not Found)”. Do I need to resolve this for debugging to work? How?

---

<div class="post-metadata">

**Author:** ![lightblade](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/lightblade/32/15632_2.png) [@lightblade](https://discuss.emberjs.com/u/lightblade)\
**Post date:** [September 30, 2014, 5:33am UTC](https://discuss.emberjs.com/t/debugging-ember-cli/6379/2 "2014-09-30T05:33:04Z")

</div>

They are complied into one file, but the source codes are actually separated due to the use of sourceURL.

Each file is compiled into a single string, then `eval` with sourceURL appended at the end. So in your dev tool, you still see them as separate files.

Try `CTRL+O` or `COMMAND+O` in your chrome dev tool’s source tab.

---

<div class="post-metadata">

**Author:** ![michaelrkn](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/michaelrkn/32/16374_2.png) [@michaelrkn](https://discuss.emberjs.com/u/michaelrkn)\
**Post date:** [September 30, 2014, 5:33am UTC](https://discuss.emberjs.com/t/debugging-ember-cli/6379/3 "2014-09-30T05:33:48Z")

</div>

1. Yes. Use `console.log()` and `debugger` just like you otherwise would. Install the [Ember Inspector](https://github.com/emberjs/ember-inspector#installation) for extra help.

2. No.

3. No.

---

<div class="post-metadata">

**Author:** ![emorling](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.emberjs.com/emorling/32/9484_2.png) [@emorling](https://discuss.emberjs.com/u/emorling)\
**Post date:** [September 30, 2014, 7:10pm UTC](https://discuss.emberjs.com/t/debugging-ember-cli/6379/4 "2014-09-30T19:10:09Z")

</div>

This is a great resource about debugging with ember:

> **[Screencast: Debugging an Ember.js Application](https://eviltrout.com/2014/08/16/debugging-ember-js.html)**
>
> I’ve found that a lot of people don’t know how powerful the Chrome Developer Tools are, especially when paired with the Ember Inspector. I recorded this short screencast to show a handful of tricks you can use when debugging Ember.js applications:

---

<div class="post-metadata">

**Author:** ![kceiw](https://avatars.discourse-cdn.com/v4/letter/k/a9adbd/32.png) [@kceiw](https://discuss.emberjs.com/u/kceiw)\
**Post date:** [November 18, 2014, 4:35pm UTC](https://discuss.emberjs.com/t/debugging-ember-cli/6379/5 "2014-11-18T16:35:20Z")

</div>

I’m also looking for a way to debug since I found it’s quite painful to debug when I use ember cli. Specifically, I cannot set a breakpoint to the code that I write since they’re put into eval() by ember-cli. Even with Ember Inspector, I cannot set a breakpoint either.