You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Request and Reasoning:
Clarification of locations of key files when installed on windows, mac and linux, for the runtime of the dev environment.
In Windows, when the global n8n launches for local development, the place for putting your custom nodes is actually found in the current user directory, not in the node modules directory itself. I may not be the sharpest knife in the kitchen when it comes to the node ecosystem, so this may be a hard case of user error during setup of the devkit, but this one stumped me for a day or two of googling until I found the answer on a form thread. For past me, I would appreciate it if there could be a note added about where the runtime config is found on windows, mac and linux.
Example: after running n8n, you can add your custom directory for installing nodes if it does exist and link your build. On windows it be found under %userprofile%/.n8n in windows explorer, or ~/.n8n in powershell.
Thanks for your consideration.
The text was updated successfully, but these errors were encountered:
URL creating-nodes/build/node-development-environment
Request and Reasoning:
Clarification of locations of key files when installed on windows, mac and linux, for the runtime of the dev environment.
In Windows, when the global n8n launches for local development, the place for putting your custom nodes is actually found in the current user directory, not in the node modules directory itself. I may not be the sharpest knife in the kitchen when it comes to the node ecosystem, so this may be a hard case of user error during setup of the devkit, but this one stumped me for a day or two of googling until I found the answer on a form thread. For past me, I would appreciate it if there could be a note added about where the runtime config is found on windows, mac and linux.
Example: after running n8n, you can add your custom directory for installing nodes if it does exist and link your build. On windows it be found under
%userprofile%/.n8n
in windows explorer, or~/.n8n
in powershell.Thanks for your consideration.
The text was updated successfully, but these errors were encountered: