Load Order Deserialization Fails Outside Error Handling if LO File Deleted?

[effs]

Looks like ENOENT is somehow escaping the TaskEither.tryCatch, might be the Task instead of a Promise?

[effs]

Can't seem to reproduce this, the error is correctly caught for me. It seems unlikely that Steam or the C: would confound the issue..

Sat, 11 Feb 2023 03:13:36 GMT - warn: [cyberpunk2077] V2077 Load Order: Failed to deserialize load order, ignoring the file: Failed to read file G:\GOG\Cyberpunk 2077\V2077\Load Order\V2077-load-order-JoXXWgtZn.json (on disk G:\GOG\Cyberpunk 2077\V2077\Load Order\V2077-load-order-JoXXWgtZn.json): Error: ENOENT: no such file or directory, open 'G:\GOG\Cyberpunk 2077\V2077\Load Order\V2077-load-order-JoXXWgtZn.json'

[effs]

[effs]

...Ok, makes sense.

1. Vortex must be running
2. One of the parent folders must be missing, not just the file
3. The failure happens on write, read handles the error fine

So adding some generic protection around the file write as required by #346 will 'solve' this problem in that we can at least show a slightly better error message.