Hey @Xavier-Cliquennois,
That is not a bad idea, I do want to get that repo updated at some point so it could just be a case of fixing the 2 examples there.
Hey @Jon
I can manage to reproduce the issue even on the n8n-nodes-digital-ocean by
using n8n 1.38.0
node: 18.18.0
remove the package-lock and node_modules (so the n8n-core and n8n-workflow will get updated to last version)
then npm install and npm run build then do the link an
it looks like it starting from n8n version 1.6.0, on 1.5.0 the same build it works.
Hey @liranp,
Welcome to the community 
That is interesting I will give it a go this afternoon and see what happens, I know that the node itself works as I am using it in 1.37 at the moment.
I am still having this issue. Any update on this?
Same issue for me
same issue here with failing to build the example repo nodes with no modifications
Node v 18
Wasted a day on this. It’s killing me. No configurations of versions or docker images or npm packages is making this message go away.
EDIT: Fixed it. The answer is roll all versions back before the enshitification of n8n, before the license rugpull. Use an older package like this as your base: GitHub - arladmin/n8n-nodes-directus
hey @Jon did you managed to reproduce? Its a big issue and the only workaround is to use old core versions which doesn’t contain all the types we need for typescript for example helpers.assertBinaryData getBinaryMetadata etc…
are you talking about the switch to Sustainable Use License back over 2 years ago?
I would not recommend using any versions of n8n that old, as they are riddled with security vulnerabilities.
It seems like a lot of custom nodes are still using n8n-core (and some even n8n), which they shouldn’t, as this creates a dependency mess.
I don’t know how or why that suggestion sneaked into the example repo, but since almost a year, all nodes packages should only depend on n8n-workflow.
If you are not sure how to tackle this, please post a link to a repo that you need help fixing, and I’ll send a pull-request to you. We can then use these PRs as examples to update the examples later 
This should fix the issue caused by the dependency mess that was caused by every node pulling in their own copy of n8n-core and n8n-workflow.
Updated n8n-nodes-digital-ocean as well stop using n8n-core in nodes by netroy · Pull Request #2 · Joffcom/n8n-nodes-digital-ocean · GitHub