# Troubleshooting Dashboard 2.0 using Vue.js devtools

**URL:** <https://discourse.nodered.org/t/troubleshooting-dashboard-2-0-using-vue-js-devtools/89325>\
**Category:** Dashboard\
**Tags:** dashboard-2\
**Created:** [6 July 2024 19:21 UTC](https://discourse.nodered.org/t/troubleshooting-dashboard-2-0-using-vue-js-devtools/89325 "2024-07-06T19:21:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vjagt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/vjagt/32/90328_2.png) [@Vjagt](https://discourse.nodered.org/u/Vjagt)\
**Post date:** [6 July 2024 19:21 UTC](https://discourse.nodered.org/t/troubleshooting-dashboard-2-0-using-vue-js-devtools/89325/1 "2024-07-06T19:21:01Z")

</div>

In trying to get a better understanding of issues I am troubleshooting in Dashboard 2.0 I have tried to install and use Vue.js devtools. When I try to use them I get **Vue.js is detected on this page.**  
Devtools inspection is not available because it's in production mode or explicitly disabled by the author.

Is this intended or is there some configuration I need to do to make the tool operate. Thanks

Do I need to build from github to make this work .... Thanks

---

<div class="post-metadata">

**Author:** ![arturv2000](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/arturv2000/32/88724_2.png) [@arturv2000](https://discourse.nodered.org/u/arturv2000)\
**Post date:** [6 July 2024 19:51 UTC](https://discourse.nodered.org/t/troubleshooting-dashboard-2-0-using-vue-js-devtools/89325/2 "2024-07-06T19:51:12Z")

</div>

It seems that is necessary to locally compile and install that version in order to use that.

With a local version, compiled in development mode `npm run build:dev` it is possible to use that extension.

Check the instructions to install locally -\> [Contributing | Node-RED Dashboard 2.0 (flowfuse.com)](https://dashboard.flowfuse.com/contributing/#installing-locally)

And is necessary to build in development mode, if using windows in the command line execute `$env:NODE_ENV="development"` before calling `npm run build`.

---

<div class="post-metadata">

**Author:** ![joepavitt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/joepavitt/32/59722_2.png) [@joepavitt](https://discourse.nodered.org/u/joepavitt)\
**Post date:** [6 July 2024 22:03 UTC](https://discourse.nodered.org/t/troubleshooting-dashboard-2-0-using-vue-js-devtools/89325/3 "2024-07-06T22:03:41Z")

</div>

I know @Steve-Mcl was, at one point, looking at adding Vue support to the in-built Monaco editor, which would help here _massively_

In the mean time, @arturv2000 is correct. Our published release to npm is a compiled/built package (more memory efficient when deployed to a Dashboard). So, to access the dev tools, etc, you would need to have a local copy of the Dashbowrd and run it in "dev mode"

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [20 July 2024 22:04 UTC](https://discourse.nodered.org/t/troubleshooting-dashboard-2-0-using-vue-js-devtools/89325/4 "2024-07-20T22:04:18Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.