n8n - 💡(How to fix) Fix cannot run dev server with npm run dev in custom node project [2 comments, 3 participants]

npm warn Unknown env config "verify-deps-before-run". This will stop working in the next major version of npm. npm warn Unknown env config "npm-globalconfig". This will stop working in the next major version of npm. npm warn Unknown env config "_jsr-registry". This will stop working in the next major version of npm. npm warn ERESOLVE overriding peer dependency npm warn While resolving: @getzep/[email protected] npm warn Found: @langchain/[email protected] npm warn node_modules/@langchain/core npm warn @langchain/core@"1.1.34" from @n8n/[email protected] npm warn node_modules/@n8n/ai-utilities npm warn @n8n/ai-utilities@"0.10.0" from [email protected] npm warn node_modules/n8n npm warn 2 more (@n8n/ai-node-sdk, @n8n/n8n-nodes-langchain) npm warn 25 more (@n8n/ai-workflow-builder, @n8n/n8n-nodes-langchain, ...) npm warn npm warn Could not resolve dependency: npm warn peerOptional @langchain/core@"~0.1.29" from @getzep/[email protected] npm warn node_modules/@getzep/zep-cloud npm warn peerOptional @getzep/zep-cloud@"^1.0.6" from @langchain/[email protected] npm warn node_modules/@n8n/ai-utilities/node_modules/@langchain/community npm warn 2 more (@n8n/n8n-nodes-langchain, @langchain/community) npm warn npm warn Conflicting peer dependency: @langchain/[email protected] npm warn node_modules/@langchain/core npm warn peerOptional @langchain/core@"~0.1.29" from @getzep/[email protected] npm warn node_modules/@getzep/zep-cloud npm warn peerOptional @getzep/zep-cloud@"^1.0.6" from @langchain/[email protected] npm warn node_modules/@n8n/ai-utilities/node_modules/@langchain/community npm warn 2 more (@n8n/n8n-nodes-langchain, @langchain/community) npm warn ERESOLVE overriding peer dependency npm warn While resolving: @browserbasehq/[email protected] npm warn Found: [email protected] npm warn node_modules/@n8n/n8n-nodes-langchain/node_modules/openai npm warn openai@"^6.9.0" from @n8n/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain npm warn @n8n/n8n-nodes-langchain@"2.16.1" from [email protected] npm warn node_modules/n8n npm warn 1 more (@langchain/community) npm warn npm warn Could not resolve dependency: npm warn peer openai@"^4.62.1" from @browserbasehq/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain/node_modules/@browserbasehq/stagehand npm warn peer @browserbasehq/stagehand@"^1.0.0" from @langchain/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community npm warn npm warn Conflicting peer dependency: [email protected] npm warn node_modules/openai npm warn peer openai@"^4.62.1" from @browserbasehq/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain/node_modules/@browserbasehq/stagehand npm warn peer @browserbasehq/stagehand@"^1.0.0" from @langchain/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community npm warn ERESOLVE overriding peer dependency npm warn While resolving: @langchain/[email protected] npm warn Found: @azure/[email protected] npm warn node_modules/@azure/search-documents npm warn @azure/search-documents@"12.1.0" from @n8n/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain npm warn @n8n/n8n-nodes-langchain@"2.16.1" from [email protected] npm warn node_modules/n8n npm warn 1 more (@langchain/community) npm warn npm warn Could not resolve dependency: npm warn peerOptional @azure/search-documents@"^12.2.0" from @langchain/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community npm warn @langchain/community@"1.1.14" from @n8n/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain npm warn npm warn Conflicting peer dependency: @azure/[email protected] npm warn node_modules/@azure/search-documents npm warn peerOptional @azure/search-documents@"^12.2.0" from @langchain/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community npm warn @langchain/community@"1.1.14" from @n8n/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain npm warn ERESOLVE overriding peer dependency npm warn While resolving: @langchain/[email protected] npm warn Found: @huggingface/[email protected] npm warn node_modules/@huggingface/inference npm warn @huggingface/inference@"4.0.5" from @n8n/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain npm warn @n8n/n8n-nodes-langchain@"2.16.1" from [email protected] npm warn node_modules/n8n npm warn npm warn Could not resolve dependency: npm warn peerOptional @huggingface/inference@"^4.13.11" from @langchain/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community npm warn @langchain/community@"1.1.14" from @n8n/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain npm warn npm warn Conflicting peer dependency: @huggingface/[email protected] npm warn node_modules/@huggingface/inference npm warn peerOptional @huggingface/inference@"^4.13.11" from @langchain/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain/node_modules/@langchain/community npm warn @langchain/community@"1.1.14" from @n8n/[email protected] npm warn node_modules/@n8n/n8n-nodes-langchain npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated [email protected]: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm warn deprecated npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm warn deprecated [email protected]: Use your platform's native DOMException instead npm warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: No longer maintained. Please contact the author of the relevant native addon; alternatives are available. npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: Package is no longer maintained npm warn deprecated [email protected]: The gm module has been sunset. Please migrate to an alternative. https://github.com/aheckmann/gm?tab=readme-ov-file#2025-02-24-this-project-is-not-maintained npm warn deprecated [email protected]: This package is deprecated. Use the optional chaining (?.) operator instead. npm warn deprecated [email protected]: Use @exodus/bytes instead for a more spec-conformant and faster implementation npm warn deprecated @aws-sdk/[email protected]: This package has moved to @smithy/signature-v4 npm warn deprecated @aws-sdk/[email protected]: This package has moved to @smithy/protocol-http npm warn deprecated @xata.io/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm warn deprecated [email protected]: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting [email protected] npm warn deprecated [email protected]: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting [email protected] npm warn deprecated [email protected]: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting [email protected] npm warn deprecated [email protected]: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting [email protected] npm warn deprecated [email protected]: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting [email protected] npm warn deprecated [email protected]: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting [email protected] npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm warn deprecated [email protected]: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting [email protected] npm warn deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm warn deprecated [email protected]: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting [email protected] npm warn deprecated [email protected]: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting [email protected] npm warn deprecated [email protected]: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting [email protected] npm warn deprecated [email protected]: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting [email protected] Error: Failed to load module "breaking-changes": Cannot find module '/home/notmrmario/.npm/_npx/83f51bd5dfda7e85/node_modules/n8n/dist/modules/breaking-changes.ee/breaking-changes.module' Require stack:

• /home/notmrmario/.npm/_npx/83f51bd5dfda7e85/node_modules/@n8n/backend-common/dist/modules/module-registry.js
• /home/notmrmario/.npm/_npx/83f51bd5dfda7e85/node_modules/@n8n/backend-common/dist/index.js
• /home/notmrmario/.npm/_npx/83f51bd5dfda7e85/node_modules/n8n/dist/config/index.js
• /home/notmrmario/.npm/_npx/83f51bd5dfda7e85/node_modules/n8n/bin/n8n. Please review the module's entrypoint file name and the module's directory name. at ModuleRegistry.loadModules (/home/notmrmario/.npm/_npx/83f51bd5dfda7e85/node_modules/@n8n/backend-common/src/modules/module-registry.ts:100:12) at CommandRegistry.execute (/home/notmrmario/.npm/_npx/83f51bd5dfda7e85/node_modules/n8n/src/command-registry.ts:46:3) at /home/notmrmario/.npm/_npx/83f51bd5dfda7e85/node_modules/n8n/bin/n8n:63:2

TL;DR

The issue is likely due to a missing or incompatible module, and resolving the peer dependency conflicts may fix the problem.

Guidance

1. Check for peer dependency conflicts: The error logs indicate several peer dependency conflicts, such as @langchain/core, openai, @azure/search-documents, and @huggingface/inference. Try to resolve these conflicts by updating the dependencies to compatible versions.
2. Verify module installation: Ensure that the breaking-changes module is installed and its entrypoint file name and directory name are correct.
3. Clean and reinstall dependencies: Run npm ci or npm install to clean and reinstall the dependencies, which may help resolve any issues with missing or incompatible modules.
4. Check for deprecated dependencies: The error logs also indicate several deprecated dependencies, such as inflight, q, and glob. Consider updating or replacing these dependencies to ensure compatibility and security.

Example

No specific code example is provided, as the issue seems to be related to dependency conflicts and module installation.

Notes

The issue may be specific to the n8n version (2.16.1) or the Node.js version (24.12.0) being used. Additionally, the error logs indicate several deprecated dependencies, which may need to be updated or replaced to ensure compatibility and security.

Recommendation

Apply a workaround by resolving the peer dependency conflicts and updating the dependencies to compatible versions. If the issue persists, consider seeking further assistance from the n8n community or support team.