Remove @babylonjs/gui-editor dependency and mark as external

[tracygardner]

Summary

This PR removes the @babylonjs/gui-editor package as a direct dependency and marks it as an external module in the Rollup build configuration. This change indicates the package is no longer bundled with the application.

Changes

• Removed @babylonjs/gui-editor from package.json dependencies
• Added @babylonjs/gui-editor to the external array in Rollup's rollupOptions configuration to prevent bundling attempts

Implementation Details

By marking the package as external in Rollup, any imports of @babylonjs/gui-editor will be treated as external dependencies rather than being bundled into the final build output. This is useful when the package is either:

• Provided by the runtime environment separately
• No longer needed in the application
• Loaded dynamically from an external source

https://claude.ai/code/session_01W3JSg9Nh34J36sZj9FnkdJ

Summary by CodeRabbit

• Chores
  • Moved an external UI/editor package out of runtime dependencies so it will no longer be installed at runtime.
  • Updated build/optimization settings to exclude that package from dependency processing and treat it as external during bundling; no public APIs or exported entities changed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 29e5e70e-a41e-48a5-a98e-8f4a7df1eadf

📥 Commits

Reviewing files that changed from the base of the PR and between 07fc630 and 0ebb72e.

📒 Files selected for processing (1)

• package.json

✅ Files skipped from review due to trivial changes (1)

• package.json

---

📝 Walkthrough

Walkthrough

Removed @babylonjs/gui-editor from runtime dependencies and updated Vite config to exclude and treat @babylonjs/gui-editor as external during optimization and bundling, preventing it from being included in the final build.

Changes

Cohort / File(s)	Summary
Dependency update package.json	Moved @babylonjs/gui-editor from dependencies to devDependencies (same version). No other metadata or scripts changed.
Build configuration vite.config.mjs	Added @babylonjs/gui-editor to optimizeDeps.exclude and listed it as external in build.rollupOptions while keeping input: "index.html". Formatting of the exclude list was adjusted.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 I nibbled lines and cleared the trail,
One package shifted, light as a tale.
Vite skips the bundle, rollup waves goodbye,
I twitch my whiskers and hum a lullaby. 🥕

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main changes: moving @babylonjs/gui-editor to devDependencies and marking it as external in Vite configuration to prevent bundling.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/externalize-gui-editor-gCjlf

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

vite.config.mjs (1)

1-305: ⚠️ Potential issue | 🟡 Minor

Prettier check is failing for this file in CI.

Pipeline reports a formatting issue in vite.config.mjs; please run Prettier and commit the formatted file to unblock checks.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@vite.config.mjs` around lines 1 - 305, Prettier formatting is failing for
vite.config.mjs; reformat the file with your project's Prettier settings (e.g.,
run prettier --write vite.config.mjs or npm/yarn format) and commit the changes
so CI passes; ensure the exported default config (export default { ... }),
plugin blocks (cssInjectedByJsPlugin, VitePWA, viteStaticCopy), and the custom
writeBundle hooks (create-flock-proxy, copy-library-files) remain functionally
unchanged after formatting.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@vite.config.mjs`:
- Around line 1-305: Prettier formatting is failing for vite.config.mjs;
reformat the file with your project's Prettier settings (e.g., run prettier
--write vite.config.mjs or npm/yarn format) and commit the changes so CI passes;
ensure the exported default config (export default { ... }), plugin blocks
(cssInjectedByJsPlugin, VitePWA, viteStaticCopy), and the custom writeBundle
hooks (create-flock-proxy, copy-library-files) remain functionally unchanged
after formatting.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f3376272-53ff-4b3c-a693-a50d45b4fe4e

📥 Commits

Reviewing files that changed from the base of the PR and between b3824be and 8d58bf2.

📒 Files selected for processing (2)

• package.json
• vite.config.mjs

💤 Files with no reviewable changes (1)

• package.json