Disable update notifications for particular nodes?

General
1

I believe that it is not currently possible to disable update notifications for particular nodes. I am using a hacked fork of a node, installed directly from github. Since the version in npm has since been updated then I get an update notification for the node, which I want to silence.

Is there any way to do this?

2

I think your only option is to adjust the version number in its package json to a slightly higher version number. (would need a NR restart - i think!)

3

I suspected that might be the only solution. Thanks.

4

If I remember correctly, the update notifications respects the node installation/update exclusion list. But I don't remember if adding the node to the update exclusion list (denyUpdateList) will remove your fork.

There's also the versioning; I remember working on it, but it's still on the very long list I'm giving to Nick :sweat_smile:

5

Magic, that fixed it, thanks.
For reference I now have in settings.js

    externalModules: {
        autoInstall: false,   /** Whether the runtime will attempt to automatically install missing modules */
        autoInstallRetry: 30, /** Interval, in seconds, between reinstall attempts */
        palette: {              /** Configuration for the Palette Manager */
            allowInstall: true, /** Enable the Palette Manager in the editor */
            allowUpdate: true,  /** Allow modules to be updated in the Palette Manager */
            allowUpload: true,  /** Allow module tgz files to be uploaded and installed */
            allowList: ['*'],
            denyList: [],
            allowUpdateList: ['*'],
            denyUpdateList: ["node-red-contrib-owfs"]
        },
//        modules: {              /** Configuration for node-specified modules */
//            allowInstall: true,
//            allowList: [],
//            denyList: []
//        }
    },

The only problem will be if I decide I do want to update it. I won't be able to work out why I can't :slight_smile:

6

add/include comments reminding you of what you did to prevent the problem.

7

where do I put the reminder that I added the comments (and where I added them)?

8

(For me...)

I'd put them as close to the top of the code as I could.

Or have a README file in the build.

I don't know the structure of git files. But it was mentioned that a fork was made.

9

You are missing the point. If I decided to revert to the published version then I would uninstall it using npm, then install it again. The issue then is that I would not get any notification if the author updated it. Even in manage palette I would not see the update.