Trace plugin dependencies via static loaders#3
Open
DmitrySharabin wants to merge 1 commit into
Open
Conversation
This was referenced Jun 10, 2026
Plugins are lazy-loaded by URL, so they sit outside the static module
graph and import-map/bundler tooling can't see their dependencies. The
autoload registry now carries a static string-literal loader per plugin
(`() => import("./<id>/plugin.js")`), passed through to the core
registry. Tooling can trace each plugin's deps; the loader still runs
only on a selector match, so nothing loads eagerly.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
DmitrySharabin
force-pushed
the
static-plugin-loaders
branch
from
18476ff to
1785839
Compare
DmitrySharabin
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Plugins are lazy-loaded by URL, so they sit outside the static module graph and import-map/bundler tooling can't trace their dependencies.
Fix
The autoload registry now carries a static string-literal loader per plugin (
() => import("./<id>/plugin.js")), passed through to the core registry. Tooling can trace each plugin's dependencies; the loader runs only on a selector match, so nothing loads eagerly.This is the architectural enabler; the markdown CDN fix (#4) builds on it.
Related PRs
loadloader@inspirejs/core/utilworkaround🤖 Generated with Claude Code