# Fuse debugging

**URL:** <https://forums.fusetools.com/t/fuse-debugging/5452>\
**Category:** How-to Discussions\
**Created:** [September 5, 2015, 8:34pm UTC](https://forums.fusetools.com/t/fuse-debugging/5452 "2015-09-05T20:34:18Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Terje\_Pedersen](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/terje_pedersen/32/243_2.png) [@Terje\_Pedersen](https://forums.fusetools.com/u/Terje_Pedersen)\
**Post date:** [September 5, 2015, 8:34pm UTC](https://forums.fusetools.com/t/fuse-debugging/5452/1 "2015-09-05T20:34:18Z")

</div>

In the web app world I’m often using Chrome developer tools. The first thing I needed to check in Fuse was what the object sent to me when clicking on a button in an Each list of buttons contained but the Fuse output only gave me Fuse.Scripting.Juraasic.Object but easy to fix:

```auto
console.log(JSON.stringify(sender));

```

Any plans for more advanced debugging tools for debugging Fuse apps?

---

<div class="post-metadata">

**Author:** ![Anders\_Lassen](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/anders_lassen/32/522_2.png) [@Anders\_Lassen](https://forums.fusetools.com/u/Anders_Lassen)\
**Post date:** [September 5, 2015, 9:05pm UTC](https://forums.fusetools.com/t/fuse-debugging/5452/2 "2015-09-05T21:05:24Z")

</div>

Yes indeed 🙂

We are working on this right now, JS debugging for iOS will roll out very soon, other platforms will follow shortly.

Debugging will be done using standard web debuggers such as Safari Web Inspector, connecting live to the device.

---

<div class="post-metadata">

**Author:** ![Mojo](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/mojo/32/167_2.png) [@Mojo](https://forums.fusetools.com/u/Mojo)\
**Post date:** [August 13, 2016, 4:12pm UTC](https://forums.fusetools.com/t/fuse-debugging/5452/3 "2016-08-13T16:12:51Z")

</div>

Is this already out? It’s so painful to debug just using the Monitor (simulator)

---

<div class="post-metadata">

**Author:** ![Anders\_Lassen](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/anders_lassen/32/522_2.png) [@Anders\_Lassen](https://forums.fusetools.com/u/Anders_Lassen)\
**Post date:** [August 13, 2016, 5:54pm UTC](https://forums.fusetools.com/t/fuse-debugging/5452/4 "2016-08-13T17:54:06Z")

</div>

Yes, it has been out for a long long time: [https://www.fusetools.com/docs/scripting/debugging](https://www.fusetools.com/docs/scripting/debugging)

Sorry for not updating this post

---

<div class="post-metadata">

**Author:** ![Mojo](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/mojo/32/167_2.png) [@Mojo](https://forums.fusetools.com/u/Mojo)\
**Post date:** [August 14, 2016, 11:49am UTC](https://forums.fusetools.com/t/fuse-debugging/5452/5 "2016-08-14T11:49:23Z")

</div>

Hi Anders, sorry, i meant chrome debugging. That page doesn’t mention anything about Chrome debuging at all. Will definitely give VSC a try, but I’d hate to install yet another software on my Machine just for debugging 😛

---

<div class="post-metadata">

**Author:** ![Edwin\_Reynoso](https://avatars.discourse-cdn.com/v4/letter/e/e99b99/32.png) [@Edwin\_Reynoso](https://forums.fusetools.com/u/Edwin_Reynoso)\
**Post date:** [August 15, 2016, 2:13am UTC](https://forums.fusetools.com/t/fuse-debugging/5452/6 "2016-08-15T02:13:38Z")

</div>

I would also love to debug with chrome devtools

---

<div class="post-metadata">

**Author:** ![Olle\_Fredriksson](https://avatars.discourse-cdn.com/v4/letter/o/e95f7d/32.png) [@Olle\_Fredriksson](https://forums.fusetools.com/u/Olle_Fredriksson)\
**Post date:** [August 15, 2016, 8:45am UTC](https://forums.fusetools.com/t/fuse-debugging/5452/7 "2016-08-15T08:45:42Z")

</div>

I just looked into this.

Since we’re using the vanilla V8 debugger protocol in Fuse, it might be possible for someone with a little Chrome Devtools know-how to make a wrapper for Fuse. It looks like someone [has done that](https://github.com/Jam3/devtool) for Node.js, and something similar should work for Fuse. Doing this is not currently in our roadmap since there are already ways to debug apps, but I’d be glad to help out in any way I can if someone wants to have a go at it.

---

<div class="post-metadata">

**Author:** ![Mojo](https://yyz1.discourse-cdn.com/flex035/user_avatar/forums.fusetools.com/mojo/32/167_2.png) [@Mojo](https://forums.fusetools.com/u/Mojo)\
**Post date:** [August 15, 2016, 9:06am UTC](https://forums.fusetools.com/t/fuse-debugging/5452/8 "2016-08-15T09:06:12Z")

</div>

> **Olle Fredriksson wrote:**
> 
> I just looked into this.
> 
> Since we’re using the vanilla V8 debugger protocol in Fuse, it might be possible for someone with a little Chrome Devtools know-how to make a wrapper for Fuse. It looks like someone [has done that](https://github.com/Jam3/devtool) for Node.js, and something similar should work for Fuse. Doing this is not currently in our roadmap since there are already ways to debug apps, but I’d be glad to help out in any way I can if someone wants to have a go at it.

THanks Olle,

At least it’s good to know there’s a possibility. If I had the know-how I would definitely contribute this functionality to the Fuse community.

Cheers
