botfront / rasa-webchat

A feature-rich chat widget for Rasa and Botfront
https://botfront.io/rasa
Apache License 2.0
945 stars 495 forks source link

Not able to clone and run the code in my local #465

Open gsanthosh887 opened 1 year ago

gsanthosh887 commented 1 year ago

Hi,

When i am trying to run the code in my local i am not able to run can anyone please suggest me how can i do that?

Grtting below error, Please suggest

npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While resolving: eslint-config-airbnb@14.1.0 npm ERR! Found: eslint@4.19.1 npm ERR! node_modules/eslint npm ERR! dev eslint@"^4.18.2" from the root project npm ERR! peer eslint@">= 4.12.1" from babel-eslint@10.1.0 npm ERR! node_modules/babel-eslint npm ERR! dev babel-eslint@"^10.1.0" from the root project npm ERR! 4 more (eslint-config-airbnb-base, eslint-config-prettier, ...) npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer eslint@"^3.15.0" from eslint-config-airbnb@14.1.0 npm ERR! node_modules/eslint-config-airbnb npm ERR! dev eslint-config-airbnb@"^14.1.0" from the root project npm ERR! npm ERR! Conflicting peer dependency: eslint@3.19.0 npm ERR! node_modules/eslint npm ERR! peer eslint@"^3.15.0" from eslint-config-airbnb@14.1.0 npm ERR! node_modules/eslint-config-airbnb npm ERR! dev eslint-config-airbnb@"^14.1.0" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! npm ERR! For a full report see: npm ERR! C:\Users\gsant\AppData\Local\npm-cache_logs\2023-06-26T22_19_30_878Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\gsant\AppData\Local\npm-cache_logs\2023-06-26T22_19_30_878Z-debug-0.log

gsanthosh887 commented 1 year ago

Can any one please suggest here?

AmberGoswami commented 11 months ago

I am also having the same issue

stale[bot] commented 5 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.