I’m importing .json export from Roam into logseq, and running into lots of errors due to filenames that are invalid on windows (e.g contain a “:” or other special characters). I see in the issue tracker a few other reports, and some older ones that suggest this bug was fixed in this past and so must have regressed. Here’s a representative bug report: ENOENT Error while Importing from Roam Research · Issue #6445 · logseq/logseq · GitHub
I tried to fix the bug myself, but am having trouble figuring out where the write is coming from. The import path seems to handle this already, but I guess it’s going through a different path.
Any suggestions where to look?