wescopeland
commented
2 years ago Hi!
Thank you for your interest. I apologize that there is no clarity about this anywhere in the repo. I'm presently tied up with other endeavors, and as a result, ScoreSplit is not currently officially supported.
If you are interested in going down the rabbit hole, I recommend trying:
npm i
npm run ng:serve
Hi,
I wanted to install ScoreSplit via command prompt in order to track scores for each stage in some MAME/Steam games I'm playing. After following the "getting started" instructions in the readme, I tried to use the npm run electron:windows command to build the application on Windows and got some error logs ( which are attached to this message).
2021-12-19T23_53_18_407Z-debug.log 2021-12-19T23_53_18_494Z-debug.log 2021-12-19T23_53_18_438Z-debug.log 2021-12-19T23_53_18_466Z-debug.log
Afterwards, I tried this in command prompt: C:\Users\mschl>npm run electron:windows
[Error: ENOENT: no such file or directory, open 'C:\Users\mschl\node_modules\@angular-devkit\build-angular\src\angular-cli-files\models\webpack-configs\browser.js'] { errno: -4058, code: 'ENOENT', syscall: 'open', path: 'C:\Users\mschl\node_modules\@angular-devkit\build-angular\src\angular-cli-files\models\webpack-configs\browser.js' }
'tsc' is not recognized as an internal or external command, operable program or batch file.
C:\Users\mschl>npm install npm WARN ancient lockfile npm WARN ancient lockfile The package-lock.json file was created with an old version of npm, npm WARN ancient lockfile so supplemental metadata must be fetched from the registry. npm WARN ancient lockfile npm WARN ancient lockfile This is a one-time fix-up, please be patient... npm WARN ancient lockfile npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: scoresplit@0.0.1 npm ERR! Found: rxjs@6.2.2 npm ERR! node_modules/rxjs npm ERR! dev rxjs@"6.2.2" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer rxjs@"^6.3.3" from @datorama/akita@1.24.3 npm ERR! node_modules/@datorama/akita npm ERR! @datorama/akita@"^1.18.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! See C:\Users\mschl\AppData\Local\npm-cache\eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\mschl\AppData\Local\npm-cache_logs\2021-12-20T00_15_44_088Z-debug-0.log
C:\Users\mschl>--force '--force' is not recognized as an internal or external command, operable program or batch file.
C:\Users\mschl>npm install npm WARN ancient lockfile npm WARN ancient lockfile The package-lock.json file was created with an old version of npm, npm WARN ancient lockfile so supplemental metadata must be fetched from the registry. npm WARN ancient lockfile npm WARN ancient lockfile This is a one-time fix-up, please be patient... npm WARN ancient lockfile npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: scoresplit@0.0.1 npm ERR! Found: rxjs@6.2.2 npm ERR! node_modules/rxjs npm ERR! dev rxjs@"6.2.2" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer rxjs@"^6.3.3" from @datorama/akita@1.24.3 npm ERR! node_modules/@datorama/akita npm ERR! @datorama/akita@"^1.18.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! See C:\Users\mschl\AppData\Local\npm-cache\eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\mschl\AppData\Local\npm-cache_logs\2021-12-20T00_19_33_302Z-debug-0.log
C:\Users\mschl>npm-install --force 'npm-install' is not recognized as an internal or external command, operable program or batch file.
C:\Users\mschl>npm install --force npm WARN using --force Recommended protections disabled. npm WARN ancient lockfile npm WARN ancient lockfile The package-lock.json file was created with an old version of npm, npm WARN ancient lockfile so supplemental metadata must be fetched from the registry. npm WARN ancient lockfile npm WARN ancient lockfile This is a one-time fix-up, please be patient... npm WARN ancient lockfile npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: @datorama/akita@1.24.3 npm WARN Found: rxjs@6.2.2 npm WARN node_modules/rxjs npm WARN dev rxjs@"6.2.2" from the root project npm WARN 16 more (@angular-devkit/build-angular, @angular/cli, ...) npm WARN npm WARN Could not resolve dependency: npm WARN peer rxjs@"^6.3.3" from @datorama/akita@1.24.3 npm WARN node_modules/@datorama/akita npm WARN @datorama/akita@"^1.18.0" from the root project npm WARN npm WARN Conflicting peer dependency: rxjs@6.6.7 npm WARN node_modules/rxjs npm WARN peer rxjs@"^6.3.3" from @datorama/akita@1.24.3 npm WARN node_modules/@datorama/akita npm WARN @datorama/akita@"^1.18.0" from the root project npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. npm WARN deprecated xmldom@0.1.31: Deprecated due to CVE-2021-21366 resolved in 0.5.0 npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated topo@2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated node-uuid@1.4.8: Use uuid module instead npm WARN deprecated items@2.1.2: This module has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version of hapi to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. npm WARN deprecated mailcomposer@4.0.1: This project is unmaintained npm WARN deprecated socks@1.1.9: If using 2.x branch, please upgrade to at least 2.1.6 to avoid a serious bug with socket data flow and an import issue introduced in 2.1.0 npm WARN deprecated joi@9.2.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated circular-json@0.5.9: CircularJSON is in maintenance only, flatted is its successor. npm WARN deprecated mailgun-js@0.18.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN deprecated nodemailer@2.7.2: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/ npm WARN deprecated buildmail@4.0.1: This project is unmaintained npm WARN deprecated uglify-es@3.3.9: support for ECMAScript is superseded by
uglify-jsas of v3.13.0 npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated request@2.75.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@2.0.6: this library is no longer supported npm WARN deprecated chokidar@2.0.4: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated axios@0.15.3: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410 npm WARN deprecated html-webpack-plugin@3.2.0: 3.x is no longer supported npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart() npm WARN deprecated chokidar@1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated chokidar@1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. npm WARN deprecated istanbul@0.4.5: This module is no longer maintained, try this instead: npm WARN deprecated npm i nyc npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives. npm WARN deprecated chokidar@1.7.0: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies. npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1 npm WARN deprecated @angular/http@6.1.2: Package no longer supported. Use @angular/common instead, see https://angular.io/guide/deprecations#angularhttp npm WARN deprecated uws@9.14.0: New code is available at github.com/uNetworking/uWebSockets.js npm WARN deprecated core-js@2.5.6: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.npm WARN using --force Recommended protections disabled. npm WARN using --force Recommended protections disabled.
• electron-builder version=20.28.1 • loaded configuration file=C:\Users\mschl\electron-builder.json Error: Unresolved node modules: @wescopeland/game-vision at C:\Users\mschl\node_modules\app-builder-lib\src\util\packageDependencies.ts:108:17 From previous event: at Collector.resolveUnresolvedHoisted (C:\Users\mschl\node_modules\app-builder-lib\src\util\packageDependencies.ts:164:10) at C:\Users\mschl\node_modules\app-builder-lib\src\util\packageDependencies.ts:82:28 at Generator.next ()
at processImmediate (node:internal/timers:464:21)
From previous event:
at Collector.collect (C:\Users\mschl\node_modules\app-builder-lib\src\util\packageDependencies.ts:84:6)
at C:\Users\mschl\node_modules\app-builder-lib\out\util\packageDependencies.js:123:47
at Generator.next ()
From previous event:
at getProductionDependencies (C:\Users\mschl\node_modules\app-builder-lib\out\util\packageDependencies.js:128:17)
at Lazy. (C:\Users\mschl\node_modules\app-builder-lib\src\util\packageDependencies.ts:31:35)
at Lazy.get value [as value] (C:\Users\mschl\node_modules\lazy-val\src\main.ts:18:25)
at C:\Users\mschl\node_modules\app-builder-lib\src\util\yarn.ts:128:81
at Generator.next ()
From previous event:
at rebuild (C:\Users\mschl\node_modules\app-builder-lib\out\util\yarn.js:239:18)
at C:\Users\mschl\node_modules\app-builder-lib\src\util\yarn.ts:20:11
From previous event:
at installOrRebuild (C:\Users\mschl\node_modules\app-builder-lib\out\util\yarn.js:68:17)
at C:\Users\mschl\node_modules\electron-builder\src\cli\install-app-deps.ts:56:9
at Generator.next ()
From previous event:
at installAppDeps (C:\Users\mschl\node_modules\electron-builder\out\cli\install-app-deps.js:174:17)
at C:\Users\mschl\node_modules\electron-builder\src\cli\cli.ts:42:48
at processImmediate (node:internal/timers:464:21)
From previous event:
at Object.handler (C:\Users\mschl\node_modules\electron-builder\src\cli\cli.ts:42:48)
at Object.runCommand (C:\Users\mschl\node_modules\yargs\lib\command.js:238:44)
at Object.parseArgs [as _parseArgs] (C:\Users\mschl\node_modules\yargs\yargs.js:1063:30)
at Object.get [as argv] (C:\Users\mschl\node_modules\yargs\yargs.js:1004:21)
at Object. (C:\Users\mschl\node_modules\electron-builder\src\cli\cli.ts:25:28)
at Module._compile (node:internal/modules/cjs/loader:1101:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:17:47
npm ERR! code 1
npm ERR! path C:\Users\mschl
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c npm run postinstall:electron && npx electron-builder install-app-deps
npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\mschl\AppData\Local\npm-cache_logs\2021-12-20T00_19_51_591Z-debug-0.log
C:\Users\mschl>npm run electron:windows
Date: 2021-12-20T00:22:15.725Z Hash: 87fb697e0d3d47de05ea Time: 2553ms chunk {0} runtime.b21b7998b455f90aab45.js (runtime) 1.05 kB [entry] [rendered] chunk {1} (styles) [initial] [rendered] chunk {2} polyfills.e7f5364b276024e19b0b.js (polyfills) 130 bytes [initial] [rendered] chunk {3} main.0594610c91de797f492a.js (main) 128 bytes [initial] [rendered]
ERROR in Module build failed: Error: Cannot find module 'node-sass' Require stack:
C:\Users\mschl\node_modules\@angular\cli\bin\ng at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15) at Function.Module._load (node:internal/modules/cjs/loader:778:27) at Module.require (node:internal/modules/cjs/loader:1005:19) at require (node:internal/modules/cjs/helpers:102:18) at getDefaultSassImpl (C:\Users\mschl\node_modules\sass-loader\dist\index.js:198:10) at Object.loader (C:\Users\mschl\node_modules\sass-loader\dist\index.js:80:29) at C:\Users\mschl\node_modules\webpack\lib\NormalModule.js:252:20 at C:\Users\mschl\node_modules\loader-runner\lib\LoaderRunner.js:367:11 at C:\Users\mschl\node_modules\loader-runner\lib\LoaderRunner.js:233:18 at runSyncOrAsync (C:\Users\mschl\node_modules\loader-runner\lib\LoaderRunner.js:143:3) at iterateNormalLoaders (C:\Users\mschl\node_modules\loader-runner\lib\LoaderRunner.js:232:2) at Array. (C:\Users\mschl\node_modules\loader-runner\lib\LoaderRunner.js:205:4)
at Storage.finished (C:\Users\mschl\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:55:16)
at C:\Users\mschl\node_modules\enhanced-resolve\lib\CachedInputFileSystem.js:91:9
at C:\Users\mschl\node_modules\graceful-fs\graceful-fs.js:123:16
at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3)
I'm not sure if I did something wrong in the process, but this seems like using command prompt is the only way to run this program at the moment ( unless there will be a stand-alone application with a UI in the future, which would make things much easier & less frustrating to set up).