# Script to trigger flow library update after npm publish?

**URL:** <https://discourse.nodered.org/t/script-to-trigger-flow-library-update-after-npm-publish/61075>\
**Category:** General\
**Created:** [10 April 2022 16:00 UTC](https://discourse.nodered.org/t/script-to-trigger-flow-library-update-after-npm-publish/61075 "2022-04-10T16:00:16Z")\
**Posts on this page:** 1\
**Showing post:** 13

<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:** [11 April 2022 06:15 UTC](https://discourse.nodered.org/t/script-to-trigger-flow-library-update-after-npm-publish/61075/13 "2022-04-11T06:15:50Z")

</div>

> [@tve](#):
>
> do you have some short write-up on how to do the step debug in vscode, preferably when using docker to run NR?

Unfortunately not using docker but you should be able to adapt my method to a remote container...

> [@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:…

If I get a moment later today or this week, I'll try with a container & let you know how it goes (no promises im afraid)

---

_[View the full topic](https://discourse.nodered.org/t/script-to-trigger-flow-library-update-after-npm-publish/61075)._