-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error loading node "runtime-blob-types" #43
Comments
Hey @technervs, Can you try running this repo to see if you get the same issue without your changes to see if you have the same issue. This will tell us if the issue is with this repo or with your custom node. |
I downloaded this repo and did the same test, I got the same errors |
Hey @technervs, I have just given it a go and I am nto able to reproduce this, Can you clear your .n8n/custom folder and try again to see if that helps or run something like |
When running the npm explain @aws-sdknpm why @AWS-SDK commands, it generated an error log: Eu já havia feito o teste de limpar a pasta n8n/custom, mas não resolveu |
I am not sure why that is still showing n8n-nodes-oraclesql in the output, Did you run the command from inside ~/.n8n/custom or in the nodes folder? |
@Joffcom the problem occurs, when trying to install newer n8n package versions (i.e. n8n-core and n8n-workflow). When using this repo as is, the outdated n8n packages < 1.0 will be installed (specified in the package-lock) and the linking works. However, when trying to install and use the latest n8n packages, this error occurs when starting n8n after linking. |
I managed to solve it in the following way, I went back to the old versions of the packages and I had to change the name of the node folder so that npm recognized it |
@technervs did you rename the |
@Joffcom I'm with the same problem here...
The problem is with
|
Hey @kimtiago, When are you seeing the error? Are you also creating a node on Windows? |
I'm seeing this error when start my n8n installed global by |
I renamed the project folder and when I use npm link it consequently changes the name of the folder in the .n8n/custom directory |
@kimtiago interesting at the moment from what I can tell this issue only appears for windows users. I will do some digging to see if this has been raised on the aws-sdk project. |
Hi @Joffcom , I've decided to stop trying to develop n8n on Windows. However, I'm now facing a different issue. On my Ubuntu 22.04 VPS, where my applications are running with Docker/Portainer/Traefik, I've set up a separate n8n instance for development purposes. I've also installed Node.js and npm directly on the server's root to work on this starter-node project. This particular n8n instance has its .n8n volume mapped out, but the 'link' command seems ineffective because the instance isn't able to recognize the project's actual path. Do you have any advice or suggestions on how to effectively work in this setup? |
I'm having this issue running Linux |
FYI, this is happening in WSL too |
I updated nodejs to version 18.18.2 and the packages to the latest version. When I run n8n at first it starts normally, but after I run the npm link n8n-nodes-oraclesql command, it starts giving these errors, I don't understand why the @AWS-SDK folder gives an error in the node_modules folder .n8n\ custom but there is no error in the n8n folder, if I delete the node_modules folder which is inside the custom folder the n8n starts normally.
I returned all package and nodejs versions to their previous versions but the error still persists.
Here are the versions of my package.json
The text was updated successfully, but these errors were encountered: