Error: ENAMETOOLONG: name too long

[jdbohrman]

Describe the problem/error/question

I’m getting a really persistent recursing directory error when trying to follow the docs for building a custom node.

What is the error message (if any)?

Error: ENAMETOOLONG: name too long, scandir '/Users/jdbohrman/.n8n/custom/node_modules/n8n-nodes-beehiiv/node_modules/n8n-nodes-beehiiv/node_modules/n8n-nodes-beehiiv/node_modules/n8n-nodes-beehiiv/node_modules/n8n-nodes-beehiiv/node_modules/n8n-nodes-beehiiv/node_modules/n8n-nodes-beehiiv/node_modules/n8n-nodes-beehiiv/node_modules/n8n-nodes-beehiiv/node_modules/n8n-nodes-beehiiv/node_modules/n8n-nodes-beehiiv/node_modules/n8n-nodes-beehiiv

Information on your n8n setup

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

[Jon]

Hey @jdbohrman,

Can you share the steps you are taking to get to this point? It looks like you might have a symlink in place.

[netroy]

@jdbohrman

.n8n/custom

.n8n/custom is for custom individual nodes.
Since you have already published the package, I’d recommend deleting .n8n/custom/node_modules/n8n-nodes-beehiiv, and installing n8n-nodes-beehiiv from the UI.

if you are developing the node locally, then you should link the package into ~/.n8n/nodes instead.

[jdbohrman]

Amazing thank you both @Jon @netroy . I’m holding off on finishing this because I want to see if Beehiiv will ever add POST functionality to the “Posts” endpoint, because for my overall usecase that is what I need, so once I finish talking to them I’m going to publish regardless based on how that convo goes. Worst case scenario I’ll publish as is and add the POST down the line