Flowise icon indicating copy to clipboard operation
Flowise copied to clipboard

Problems with installation.I need help with this.

Open 8draco8 opened this issue 1 year ago • 23 comments

npm install -g flowise

설치 중에서 이런 에러가 나타난다.

E:\aiprogram\Flowise>npm install -g flowise npm warn ERESOLVE overriding peer dependency npm warn While resolving: [email protected] npm warn Found: @google/[email protected] npm warn node_modules/flowise/node_modules/llamaindex/node_modules/@google/generative-ai npm warn @google/generative-ai@"^0.8.0" from [email protected] npm warn node_modules/flowise/node_modules/llamaindex npm warn llamaindex@"^0.2.1" from [email protected] npm warn node_modules/flowise/node_modules/flowise-components npm warn npm warn Could not resolve dependency: npm warn peerOptional @google/generative-ai@"^0.1.1" from [email protected] npm warn node_modules/flowise/node_modules/llamaindex/node_modules/chromadb npm warn chromadb@"~1.7.3" from [email protected] npm warn node_modules/flowise/node_modules/llamaindex npm warn npm warn Conflicting peer dependency: @google/[email protected] npm warn node_modules/@google/generative-ai npm warn peerOptional @google/generative-ai@"^0.1.1" from [email protected] npm warn node_modules/flowise/node_modules/llamaindex/node_modules/chromadb npm warn chromadb@"~1.7.3" from [email protected] npm warn node_modules/flowise/node_modules/llamaindex npm warn EBADENGINE Unsupported engine { npm warn EBADENGINE package: '[email protected]', npm warn EBADENGINE required: { node: '>=18.15.0 <19.0.0 || ^20' }, npm warn EBADENGINE current: { node: 'v22.1.0', npm: '10.7.0' } npm warn EBADENGINE } npm warn deprecated [email protected]: cross-spawn no longer requires a build toolchain, use it instead npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead. npm warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs npm warn deprecated [email protected]: Use mz or fs-extra^3.0 with Promise Support npm warn deprecated [email protected]: < 21.9.0 is no longer supported npm warn deprecated [email protected]: Use your platform's native DOMException instead npm warn deprecated [email protected]: Use your platform's native atob() and btoa() methods instead npm warn deprecated [email protected]: The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm. npm warn deprecated @oclif/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Version no longer supported. Upgrade to @latest npm warn deprecated [email protected]: < 21.9.0 is no longer supported npm warn cleanup Failed to remove some directories [ npm warn cleanup [ npm warn cleanup 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\sqlite3', npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\sqlite3'] { npm warn cleanup errno: -4082, npm warn cleanup code: 'EBUSY', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\sqlite3' npm warn cleanup } npm warn cleanup ], npm warn cleanup [ npm warn cleanup 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\faiss-node', npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\faiss-node'] { npm warn cleanup errno: -4082, npm warn cleanup code: 'EBUSY', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\faiss-node' npm warn cleanup } npm warn cleanup ], npm warn cleanup [ npm warn cleanup 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\grpc-tools', npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\grpc-tools'] { npm warn cleanup errno: -4082, npm warn cleanup code: 'EBUSY', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\grpc-tools' npm warn cleanup } npm warn cleanup ], npm warn cleanup [ npm warn cleanup 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\canvas', npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\canvas'] { npm warn cleanup errno: -4082, npm warn cleanup code: 'EBUSY', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\canvas' npm warn cleanup } npm warn cleanup ], npm warn cleanup [ npm warn cleanup 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules', npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\canvas'] { npm warn cleanup errno: -4082, npm warn cleanup code: 'EBUSY', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\canvas' npm warn cleanup } npm warn cleanup ], npm warn cleanup [ npm warn cleanup 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise', npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\faiss-node'] { npm warn cleanup errno: -4082, npm warn cleanup code: 'EBUSY', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\faiss-node' npm warn cleanup } npm warn cleanup ], npm warn cleanup [ npm warn cleanup 'C:\Users\DRACO\AppData\Roaming\npm\node_modules', npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\llamaindex\node_modules'] { npm warn cleanup errno: -4048, npm warn cleanup code: 'EPERM', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: 'C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\llamaindex\node_modules' npm warn cleanup } npm warn cleanup ] npm warn cleanup ] npm error code 1 npm error path C:\Users\DRACO\AppData\Roaming\npm\node_modules\flowise\node_modules\sharp npm error command failed npm error command C:\Windows\system32\cmd.exe /d /s /c (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy) npm error sharp: Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.14.5/libvips-8.14.5-win32-x64.tar.br npm error sharp: Please see https://sharp.pixelplumbing.com/install for required dependencies npm error sharp: Installation error: aborted

npm error A complete log of this run can be found in: C:\Users\DRACO\AppData\Local\npm-cache_logs\2024-05-11T04_36_47_439Z-debug-0.log

windows 11/ node v22.1.0 / npm 10.7.0

I deleted the node and tried both reinstalling and downgrading, but it didn't work.I need help with this.

8draco8 avatar May 11 '24 05:05 8draco8

this looks like some error with node-gyp, can you try npm install -g node-gyp ?

HenryHengZJ avatar May 13 '24 13:05 HenryHengZJ

I have the same issue

zhaoyong5555 avatar May 14 '24 03:05 zhaoyong5555

I tried npm install -g node-gyp and it didn't work, so I'm running it in docker.

8draco8 avatar May 14 '24 08:05 8draco8

Clean install of node.js version 20.16.0, got the following:

% npm i flowise npm warn ERESOLVE overriding peer dependency npm warn While resolving: @mui/[email protected] npm warn Found: [email protected] npm warn node_modules/react npm warn peerOptional react@">=17.0.0" from [email protected] npm warn node_modules/flowise-components/node_modules/lunary npm warn lunary@"^0.6.16" from [email protected] npm warn node_modules/flowise-components npm warn 30 more (flowise-ui, lunary, @emotion/react, @emotion/styled, ...) npm warn npm warn Could not resolve dependency: npm warn peer react@"^17.0.2" from @mui/[email protected] npm warn node_modules/@mui/icons-material npm warn @mui/icons-material@"5.0.3" from [email protected] npm warn node_modules/flowise-ui npm warn npm warn Conflicting peer dependency: [email protected] npm warn node_modules/react npm warn peer react@"^17.0.2" from @mui/[email protected] npm warn node_modules/@mui/icons-material npm warn @mui/icons-material@"5.0.3" from [email protected] npm warn node_modules/flowise-ui npm warn ERESOLVE overriding peer dependency npm warn deprecated [email protected]: cross-spawn no longer requires a build toolchain, use it instead npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead. npm warn deprecated [email protected]: Package is no longer maintained npm warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported 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]: Use mz or fs-extra^3.0 with Promise Support 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]: Use your platform's native DOMException instead npm warn deprecated [email protected]: Use your platform's native atob() and btoa() methods instead npm warn deprecated [email protected]: This package is no longer supported. npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported npm warn deprecated @aws-sdk/[email protected]: This package has moved to @smithy/protocol-http npm warn deprecated @aws-sdk/[email protected]: This package has moved to @smithy/signature-v4 npm warn deprecated [email protected]: The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm. npm warn deprecated [email protected]: < 22.8.2 is no longer supported npm warn deprecated @oclif/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated [email protected]: Critical bug fixed in v3.0.1, please upgrade to the latest version. 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]: This package is no longer supported. npm warn deprecated [email protected]: Version no longer supported. Upgrade to @latest

Eric-Catalyst avatar Aug 08 '24 23:08 Eric-Catalyst

I'm getting a very similar set of errors. I'm familiar with command line but new to node and JS. I updated node but am not really sure where to go from here. Also when it's done and I try "npx flowise start" I get the following error: C:\Users\Bill>npx flowise start » ModuleLoadError: [MODULE_NOT_FOUND] require failed to load » C:\Users\Bill\node_modules\flowise\dist\commands\start.js: Cannot find module 'langchainhub' » Require stack: » - C:\Users\Bill\node_modules\flowise\dist\index.js » - C:\Users\Bill\node_modules\flowise\dist\commands\start.js » - C:\Users\Bill\node_modules@oclif\core\lib\module-loader.js » - C:\Users\Bill\node_modules@oclif\core\lib\config\plugin.js » - C:\Users\Bill\node_modules@oclif\core\lib\config\config.js » - C:\Users\Bill\node_modules@oclif\core\lib\config\index.js » - C:\Users\Bill\node_modules@oclif\core\lib\command.js » - C:\Users\Bill\node_modules@oclif\core\lib\index.js » - C:\Users\Bill\node_modules\flowise\bin\run » Code: MODULE_NOT_FOUND

So i tried "npm install -g langchainhub" which says it installed a pkg but I get the same error. I'm not sure where it's calling langchainhub from but I assume I just installed it in the wrong directory?

BillTheMaker avatar Aug 10 '24 22:08 BillTheMaker

Same issue here. It must have been the last update or something, because I was installing it over a week ago and it worked fine. I did a clean install now and get the dependency hell

dotbrt avatar Aug 13 '24 08:08 dotbrt

Looking at this ticket and comparing with my experience installing Flowise recently, it seems the node-gyp issue that is the root cause of this issue has been resolved, so this issue should be closed. However, the dependency issues and use of unsupported packages with critical security issues is a major problem, and needs a separate issue report of its own.

I am a bit concerned that it seems both pull requests and issues are staying open for long periods of time with no activity in this project.

Eric-Catalyst avatar Aug 13 '24 14:08 Eric-Catalyst

Facing the same problem. Installed 2.0.4, had some problems with pgvector not working anymore, tried to switch to 1.8.4, but only 2.0.2 is installed and available.

Astriel avatar Aug 13 '24 19:08 Astriel

Had the same problem. Solved it with

npm i -g langchainhub

morigs avatar Oct 01 '24 07:10 morigs

Had the same problem. Solved it with

npm i -g langchainhub

This works for me. Thank you!

jinsanity07git avatar Oct 04 '24 21:10 jinsanity07git

Had the same problem. Solved it with

npm i -g langchainhub

Thanks. This worked for me.

monishkumar7 avatar Oct 22 '24 17:10 monishkumar7