Skip to content

Let plugins supply their own static import() loader#2

Open
DmitrySharabin wants to merge 1 commit into
mainfrom
static-plugin-loaders
Open

Let plugins supply their own static import() loader#2
DmitrySharabin wants to merge 1 commit into
mainfrom
static-plugin-loaders

Conversation

@DmitrySharabin

@DmitrySharabin DmitrySharabin commented Jun 10, 2026

Copy link
Copy Markdown
Member

Problem

Plugins are loaded by URL, so they sit outside the static module graph and import-map/bundler tooling can't trace their dependencies.

Fix

load() honors an optional load thunk on the registry entry (a static import()), falling back to URL loading for plugins known only by base.

Related PRs

Coordinated change across the repos:

🤖 Generated with Claude Code

Plugins are loaded by URL, so import-map/bundler tooling can't trace
their dependencies. load() now honors an optional `load` thunk on the
registry entry (a static import()), falling back to URL loading for
plugins known only by `base`.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant