JavaScript error: `ObjectKeyValidationError: Validation of object failed at key options.` using latest version

[MikeChongCan]

app.js?mtime=1735577165:8633 ObjectKeyValidationError: Validation of object failed at key options.
    at app.js?mtime=1735577165:8604:25
    at _Ok.and_then (app.js?mtime=1735577165:8333:12)
    at getScriptTagValue (app.js?mtime=1735577165:8426:37)
    at init3 (app.js?mtime=1735577165:47506:19)
    at app.js?mtime=1735577165:47534:1Caused by: ObjectKeyValidationError: Validation of object failed at key filename.
    at Object.options (app.js?mtime=1735577165:8604:25)
    at app.js?mtime=1735577165:8600:40
    at _Ok.and_then (app.js?mtime=1735577165:8333:12)
    at getScriptTagValue (app.js?mtime=1735577165:8426:37)
    at init3 (app.js?mtime=1735577165:47506:19)
    at app.js?mtime=1735577165:47534:1Caused by: PrimitiveValidationError: Validation of primitive string failed.
    at Object.string (app.js?mtime=1735577165:8514:67)
    at Object.options (app.js?mtime=1735577165:8600:40)
    at app.js?mtime=1735577165:8600:40
    at _Ok.and_then (app.js?mtime=1735577165:8333:12)
    at getScriptTagValue (app.js?mtime=1735577165:8426:37)
    at init3 (app.js?mtime=1735577165:47506:19)
    at app.js?mtime=1735577165:47534:1

[eriteric]

Same here. I used a default/minimal beancount file to make sure it wasn't a syntax issue...

[valychbreak]

Quite late but the issue might be related to the wrong path to your beancount file.

I've switched to a different approach of building fava docker image, but faced the same issue. Fixed by providing a file relative to docker image content:

docker run -d --name=fava-beancount-with-dashboards \
    -v your/local/path/to/beancount-file:/bean/beancount-file \
    -p 5000:5000 valychbreak/fava:1.30.7-test1 \
    /bean/beancount-file

• your/local/path/to/beancount-file - path to your beancount file with entries on your laptop/machine
• /bean/beancount-file - path to beancount file mounted to docker image
• The fix is the last argument /bean/beancount-file which is equivalent to what you provide when running fava locally fava <beancount file>. If either of the paths are wrong, you'll see that error again, so make sure they are correct.