Skip to content

chore: esm sample - #4342

Closed
ScriptedAlchemy wants to merge 6 commits into
masterfrom
esm-output
Closed

ScriptedAlchemy wants to merge 6 commits into
masterfrom
esm-output

Conversation

@ScriptedAlchemy

Copy link
Copy Markdown
Member

No description provided.

@ScriptedAlchemy

Copy link
Copy Markdown
Member Author

Closing this stale ESM sample branch rather than trying to merge it as-is.

Current state:

  • mergeable=CONFLICTING / mergeStateStatus=DIRTY
  • no current check rollup
  • maintainerCanModify=false
  • includes large stale dependency/lockfile churn

The useful salvage is a clean ESM remote-entry example rebuilt on current master/current deps, not this branch wholesale. Carry forward the ESM configuration ideas only:

  • Rsbuild host/remote with module script output, remote type/module entry loading, and the host actually consuming remote/App
  • remote output with runtime:false, filename static/remoteEntry.js, library.type=module, topLevelAwait/outputModule/module chunk loading
  • direct Rspack module-output remote config and React JSX runtime sharing

TraceDecay/core check: current runtime-core still supports remoteInfo.type 'esm'/'module' through dynamic import(entry), but the imported remote must still present the expected container shape with get/init. A replacement PR should demonstrate that current API path directly and regenerate lockfiles from current deps.

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