# How to get errors/exceptions while developing custom node?

**URL:** <https://discourse.nodered.org/t/how-to-get-errors-exceptions-while-developing-custom-node/23830>\
**Category:** Developing Nodes\
**Tags:** debugging\
**Created:** [29 March 2020 13:28 UTC](https://discourse.nodered.org/t/how-to-get-errors-exceptions-while-developing-custom-node/23830 "2020-03-29T13:28:43Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [29 March 2020 18:53 UTC](https://discourse.nodered.org/t/how-to-get-errors-exceptions-while-developing-custom-node/23830/8 "2020-03-29T18:53:28Z")

</div>

I use VSCode (as do the Devs of node-red - I think)

Yes you can debug step your server side code.

For client side, put `debugger` statements in your code and open dev tools F12.

See this...

> [@How to proper debug custom node](https://discourse.nodered.org/t/how-to-proper-debug-custom-node/9308/13):
>
> This is how I debug a custom node in VS Code... It works for me however since this is a dist version of node-red its difficult sometimes to debug client side issues. Other than that, debug stop points work in my node js files. For debuging my .html files, i enter debugger into the function & open F12 (chrome debugger stops on the debugger statement) Setup... Install node-red as per instructions on [nodered.org](http://nodered.org) Run it one time so that .node-red folder is generated Install own node... cd c:…

---

_[View the full topic](https://discourse.nodered.org/t/how-to-get-errors-exceptions-while-developing-custom-node/23830)._