-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't get the app to run #65
Comments
I get the same error. |
@DiabloSenpai #68 -- this fixes it. If this doesn't get merged you can run it run my branch here in the mean time (may need to follow the other instructors in the PR too): https://github.com/gregghz/forza-telemetry |
@gregghz i get a build error 1 The build failed. Fix the build errors and run again. |
@Zaahid15 can you provide more output? What did you try when you got that build error? |
I have followed all the steps. I have installed .net on my pc:
C:\Users<user>\OneDrive\Desktop>dotnet --list-sdks
6.0.416 [C:\Program Files\dotnet\sdk]
Then used git to clone the repository to my local machine and then I ran npm install in forza-telemtry directory:
C:\Users<user>\OneDrive\Desktop\forza-telemetry>npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: custom-electron-titlebar@3.2.7
npm ERR! Found: electron@13.1.7
npm ERR! node_modules/electron
npm ERR! dev electron@"^13.1.7" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer electron@"^10.0.0 || ^11.0.0 || ^12.0.0" from custom-electron-titlebar@3.2.7
npm ERR! node_modules/custom-electron-titlebar
npm ERR! custom-electron-titlebar@"^3.2.7" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: electron@12.2.3
npm ERR! node_modules/electron
npm ERR! peer electron@"^10.0.0 || ^11.0.0 || ^12.0.0" from custom-electron-titlebar@3.2.7
npm ERR! node_modules/custom-electron-titlebar
npm ERR! custom-electron-titlebar@"^3.2.7" 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<user>\AppData\Local\npm-cache_logs\2023-11-09T16_25_45_373Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: C:\Users<user>\AppData\Local\npm-cache_logs\2023-11-09T16_25_45_373Z-debug-0.log
Is it a problem on my part? Am I missing something?
The text was updated successfully, but these errors were encountered: