Intermittent startup error: Cannot read properties of undefined (reading '1')`

[asv55]

First of all, thank you so much for this powerful and useful plugin. I actively use it to create interactive components, and it tremendously expands the capabilities of Obsidian.

I would like to report a complex, intermittent error that occurs on Obsidian startup.

The Problem:

Periodically, upon starting Obsidian, the following errors appear in the developer console:

Uncaught (in promise) Cannot read properties of undefined (reading '1') at plugin:datacore:39455
Datacore: Failed to import file: Cannot read properties of undefined (reading '1')

The key point is that the error is intermittent (floating). With the exact same set of files in the vault, it sometimes appears and sometimes disappears after a restart.

What I've Already Tried to Diagnose (a detective story):

1. .jsx Scripts: The problem persists even when the user scripts folder is completely empty.
2. Plugin Settings: We checked all settings, including Empty values, changing them to safe defaults (-) — it didn't help.
3. YAML (frontmatter) Errors: Using the Linter plugin and custom DataviewJS scripts, we found and fixed several files with YAML syntax errors. This did not solve the problem.
4. Incorrect Inline Fields: We wrote a precise diagnostic script that found about 960 incorrectly formatted inline fields in my vault (a legacy from a Logseq import, using key:: value syntax without brackets). Using VS Code, we fixed all 960 of these errors. The diagnostic script now reports 0 issues, but the Datacore startup error remains.
5. False Positives: We found a few documentation notes where :: and ::: syntax is used in code examples and text. We tried to "hide" it from the parser (by changing code block language, escaping text). This also did not help.
6. Performance Settings: Setting "Importer threads" to 1 did not change the situation.

My Question:

Could you suggest any other debugging methods we could try? Perhaps there's a way to enable more detailed logging during startup to track which specific file or stage is causing the failure?

My Environment:

• Datacore: Version: 0.1.28
• Obsidian Version: 1.9.12
• Operating System: macOS 26

Thank you again for your work. The plugin is magnificent, and I'm eager to help resolve this issue.