build(examples): separate browser bundles from CommonJS output - #28095
build(examples): separate browser bundles from CommonJS output#28095Jason Hartman (jason-ha) wants to merge 1 commit into
Conversation
Reserve dist for CommonJS package output and emit webpack-generated browser artifacts into bundle directories instead. Serve downstream application assets from /app while keeping the webpack-fluid-loader runtime under /code, and translate Fluid UMD manifest paths to the development URL namespace. Update example webpack configurations, UMD metadata, clean scripts, ignores, and generated-output handling to follow the new convention. Ensure webpack-fluid-loader builds both module formats before downstream webpack tasks consume its CommonJS configuration. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 72fc25d5-4cc2-4f20-b0b1-f6eec93165b0
github-actions
Bot
added
base: main
|
Hi! Thank you for opening this PR. Want me to review it? Based on the diff (218 lines, 84 files), I've queued these reviewers:
How this works
|
There was a problem hiding this comment.
Copilot reviewed 83 out of 84 changed files in this pull request and generated no comments.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Bundle size comparisonBase commit: unresolved The PR's CI build failed — fix the build and the comment will update once the next run succeeds. |
distfor CommonJS package output and emit webpack-generated browser artifacts intobundledirectories instead./appwhile keeping thewebpack-fluid-loaderruntime under/code, and translate Fluid UMD manifest paths to the development URL namespace.Update example webpack configurations, UMD metadata, clean scripts, ignores, and generated-output handling to follow the new convention.
Copilot-Session: 72fc25d5-4cc2-4f20-b0b1-f6eec93165b0