New node building and the node not appear im workflow

Questions
,
1

Describe the problem/error/question

Im building a new node in n8n but when i run command start n8n the browser open but my node not available in action i search my new created node but we couldn’t found




## Information on your n8n setup

- **Running n8n via npm
- **Operating system:**
window
3

Hi @Waqas_Shaukat, welcome to the community. I am sorry you’re having trouble.

Can you confirm what exactly one would need to do to reproduce your problem? Have you linked your node using npm link?

4

Hi @MutedJam Thanks for the reply. Yes I have linked node using npm link command I do all steps mentioned in node building documentation.

image
image2827×1919 484 KB

5

Hey @Waqas_Shaukat,

Can you share the exact commands you ran and the directories you ran them in?

6

Hi @Jon,
I shared the screenshot.

7

Hey @Waqas_Shaukat,

Perfect, second npm link command you are running is being done in the wrong folder. This needs to be ran from the n8n custom folder or the nodes folder which is usually ~/.n8n/custom or ~/.n8n/nodes.

You can find information on running nodes locally here: Run your node locally | n8n Docs

8

Hey @Jon we couldn’t find the folder. Where can we find this way?
~/.n8n/custom or ~/.n8n/nodes .

image
image868×1725 83.1 KB

9

Hey @Waqas_Shaukat,

On Windows if your username was waqas the folders would be under something like C:\Users\waqas\.n8n, It will be a hidden folder as well.

10

hey @Jon there is no folder named custom in .n8n

image
image1963×742 53.9 KB

11

Hi @Jon i created folder custom and follow the documentation now i get this error.

image
image2699×1114 291 KB

12

Hey @Waqas_Shaukat,

Perfect so that looks like there could be an issue in your node with the aws-sdk package being pulled in from somewhere and it might not want to play ball with Windows.

13

So now what can we do to fix this error.

14

Hey @Waqas_Shaukat,

You would need to check your nodes project to see why it might be using that it could be that you need to update a dependency.

It could also be worth trying to run it in docker to see if it is just a windows only issue.

1 Like