Issue in installing FlowiseAI on my mac

[whhkhaled]

hello everyone,

when i tried to install Flowise on my device:

I downloaded and installed node-v20.12.1.pkg

than in the termainal i type this ( npm install -g flowise ) but after that i belive there is an error, and also i tried sudo npm install -g flowise, also same error, please see the attached screenshot

you can find also here the full Log: 2024-04-10T01_09_03_411Z-debug-0.log

npm ERR! code EACCES npm ERR! syscall mk dir npm ERR! path /usr/local/lib/node_modules/flowise npm ERR! errno -13 npm ERR! Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/flowise' npm ERR! [Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/flowise'] { npm ERR! errno: -13, npm ERR! code: 'EACCES', npm ERR! syscall: 'mkdir', npm ERR! path: '/usr/local/lib/node_modules/flowise' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It is likely you do not have the permissions to access this file as the current user npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in: /Users/khaled/.npm/_logs/2024-04-10T00_46_49_779Z-debug-0.log (base) khaled@Khaleds-MBP ~ % sudo npm install -g flowise Password: npm WARN deprecated [email protected]: cross-spawn no longer requires a build toolchain, use it instead 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 @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]: Use your platform's native DOMException instead 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]: Use your platform's native atob() and btoa() methods instead 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]: < 21.8.0 is no longer supported npm WARN deprecated [email protected]: < 21.8.0 is no longer supported 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]: Use mz or fs-extra^3.0 with Promise Support 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 @npmcli/[email protected]: This functionality has been moved to @npmcli/fs npm WARN deprecated [email protected]: Version no longer supported. Upgrade to @latest npm ERR! code ECONNRESET npm ERR! network aborted npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config'

npm ERR! A complete log of this run can be found in: /Users/khaled/.npm/_logs/2024-04-10T01_00_43_617Z-debug-0.log (base) khaled@Khaleds-MBP ~ % sudo npm install -g flowise Password: npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs 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 @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 @oclif/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN deprecated [email protected]: Use your platform's native atob() and btoa() methods instead npm WARN deprecated [email protected]: Use your platform's native DOMException instead npm WARN deprecated [email protected]: Use mz or fs-extra^3.0 with Promise Support npm WARN deprecated [email protected]: cross-spawn no longer requires a build toolchain, use it 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 [email protected]: < 21.8.0 is no longer supported npm WARN deprecated [email protected]: < 21.8.0 is no longer supported npm WARN deprecated [email protected]: Version no longer supported. Upgrade to @latest npm ERR! code ECONNRESET npm ERR! syscall read npm ERR! errno -54 npm ERR! network read ECONNRESET npm ERR! network This is a problem related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config'

npm ERR! A complete log of this run can be found in: /Users/khaled/.npm/_logs/2024-04-10T01_09_03_411Z-debug-0.log (base) khaled@Khaleds-MBP ~ %

Please advice me what i should to do, thank you

[toi500]

You only needed to read your own logs to know what is going on.

[LiBytes]

use sudo.

It solved mine

[MeinDeutschkurs]

I ran into the same issue. Why not simply write to the quick start-document MacOS: sudo npm install -g flowise into the documentation? Or why not denying the installation, if there is no way to create the target folder (in the first few lines of the install script)?

[Eric-Catalyst]

Flowise does not need to be installed globally, so try removing the -g flag.