That is a good question and I do unfortunately not know the answer to that. Perhaps @marcus knows more.
In general, could you please make sure to provide all relevant information when opening a new topic here on the forum? There’s a template for this and it’ll greatly simplify things for everyone trying to help.
The Custom nodes cannot be included in the NODES_INCLUDE or EXCLUDE docker property. If we add our Custom node types into this, then a error will be thrown in LoadNodesAndCredentials.ts file postProcessLoaders method. The error is due to the Claaname and sourcePath will be undefined in known.nodes. So I provided a temporary fix in my local but its not very ideal. But it works for me as of now.
In runDiectoryLoader function if the loader is a instaceof CustomDirectoryLoader then I will reinitialize the loader Object by passing empty arrays into the constructor for node_includes and node_excludes.
This solves the problem temporarily. Please let me know your thoughts on this.
I am a bit confused by this one, What are you actually trying to do? If you are using a custom image or manually installing nodes into the ~/.n8n/nodes folder wouldn’t the best solution be to either install them or not install them rather than using the env option?
Thats correct. I believe, its not how n8n works now. I am installing a custom node in .n8n/custom and also I want to restrict some of the base nodes that were getting displayed in the n8n, then the custom nodes also go missing.
I have created N8N-6225 as the internal ticket for this one, What you are doing might work but it may not be the option we take so I would say if it works ok for you run with it but don’t be surprised if we did something different when we change it.