Skip to content
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

Cannot parse config file: 'C:\Users\jaide\osu-ahr\config\local.json': SyntaxError: Unexpected token k in JSON at position 173 #167

Open
kzwa01 opened this issue Nov 14, 2023 · 1 comment

Comments

@kzwa01
Copy link

kzwa01 commented Nov 14, 2023

i get this everytime i try running osu-ahr

C:\Users\jaide\osu-ahr>npm start

> [email protected] start
> node dist/cli/index.js

Loading log4js configuration from ./config/log_cli.json
C:\Users\jaide\osu-ahr\node_modules\config\lib\config.js:844
    throw new Error("Cannot parse config file: '" + fullFilename + "': " + e3);
    ^

Error: Cannot parse config file: 'C:\Users\jaide\osu-ahr\config\local.json': SyntaxError: Unexpected token k in JSON at position 173
    at util.parseFile (C:\Users\jaide\osu-ahr\node_modules\config\lib\config.js:844:11)
    at C:\Users\jaide\osu-ahr\node_modules\config\lib\config.js:644:26
    at Array.forEach (<anonymous>)
    at util.loadFileConfigs (C:\Users\jaide\osu-ahr\node_modules\config\lib\config.js:643:16)
    at new Config (C:\Users\jaide\osu-ahr\node_modules\config\lib\config.js:116:27)
    at Object.<anonymous> (C:\Users\jaide\osu-ahr\node_modules\config\lib\config.js:1492:31)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)

Node.js v18.17.1
@xayanide
Copy link
Contributor

xayanide commented Dec 4, 2023

hi there! It looks like there might be a problem with the local.json file based on the error log. It seems there could be mistakes or changes in the way it's written.

could you try creating a new local.json file by copying the content from default.json? After that, set only your credentials, give it another shot and see if it works.

if you can, please share the content of that local.json file here, but please be sure to EXCLUDE any sensitive information like credentials.

please provide more information on this as it is currently not enough for me to conclude what the problem actually is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants