Plugin loader incorrectly parses strings/comments as imports
Cluster 116631. Data as of
Nothing open on GitHub. Fix merged in #117610 on 20 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #117610. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117610. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the plugin specifier or import scanner reads string literals and comments as real import statements, causing false load-blocking or source corruption. The members address scoping the scan to actual code only.
Open issues0
Open PRs0
Fixes on record
-
#117610 fix(desktop): plugin loader no longer reads strings/comments as imports (#116631, salvage #116368)
files:
apps/desktop/src/contrib/runtime-loader.test.ts,apps/desktop/src/contrib/runtime-loader.ts
1 PR closed without merging
From the close comments: merged via another change 1
-
#116368 fix(desktop): scope plugin specifier scanning to code, not strings/comments · merged via another change →
5171ea1,#117610
Closed issues · 1
- Closed#116631[Bug]: plugin runtime loader reads strings/comments as imports — false load-block and source corruption
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #117610
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026