Cannot get rid of custom node

Questions
1

Hello,

I am fine tuning my first custom node. It was a pleasure to develop.
It works perfectly in local but I am having trouble to make it work using npm.
It sounds like some files are not found / imported correctly.

But for the moment, I am having a very weird issue.
I uninstalled completely my custom node from my n8n instant, and it still appears in the node list, no matter what I do.

I tried to restart docker, to prune docker… I cannot get ride of a weird version of my custom plugin so I am having hard time to debug it.

Is there a way to “refresh cache” for all custom nodes ?

Thanks in advance

Information on your n8n setup

  • n8n version: 1.39.1
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: main):
  • Running n8n via (Docker):
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

It is really weird.
It sounds like there is a layer of client side cache for the nodes ?

When i access in private navigation, I don’t see the custom node.

So I tried to clean the cache in my main navigation, but nothing makes it vanish.

There is something strange here :smiley:

4

I am a bit lost with publishing custom node.
It looks like there are several layers of cache and I am not sure how to test that everything is working properly.

When I load my node from npm, in my local n8n instance, it works well, but when I do the same from my self-hosted docker instance. Nothing works.

Can someone test this node, and see if it loads ?

Thank you !

5

I just downloaded it and everything looks to be working fine for me on 1.38.2.

I don’t have a credential so i couldn’t test functionality, only the ui.

I have never had that issue in docker. it might have just gone to the wrong place. Try looking for it in your file structure within your container. If you really can’t find it and don’t want to start a new volume then you can rename the npm package and that should work, if that is your issue anyway

6

I would also try a stop then start of the container rather than a restart to see if that changes anything as sometimes a restart does odd things.

7

Thank you, @Jon. I tried to stop and start again. It did not change.

I am glad it works for you, @Liam.
I tried on another instance, and it works there too. But something is stuck that I don’t understand. The node does not disappear from n8n. But in private navigation, it’s not there. I cleaned the cache and did everything I could think of. It stays.

Not a big deal, but a weird case, probably complicated by different cache layers.

Thanks for your inputs!

8

The custom node disappeared by itself after a few days.
It must have been some mysterious cache issue (as often in coding).

I mark this as solved since I don’t think we will investigate this further.

1 Like
9

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