Skip to content

Switch host build to vite#4019

Draft
ef4 wants to merge 32 commits intomainfrom
vite
Draft

Switch host build to vite#4019
ef4 wants to merge 32 commits intomainfrom
vite

Conversation

@ef4
Copy link
Contributor

@ef4 ef4 commented Feb 18, 2026

No description provided.

ef4 added 21 commits December 10, 2025 18:19
These imports in app.ts were skipping a level in the package dependency graph. ember-power-select and ember-power-calendar are not dependencies of host, they're dependencies of boxel-ui.

Trying to import from your dep's deps is unreliable and makes the vite depscan complain.

I pushed them down into the boxel-ui components that actually pull the corresponding ember-power-* components into the project.
Under vite, we don't use an AMD loader so we won't conflict with the one in monaco.
@github-actions
Copy link

github-actions bot commented Feb 18, 2026

Host Test Results

    1 files  ±  0    1 suites  ±0   1h 3m 55s ⏱️ - 35m 28s
1 015 tests  - 863  975 ✅  - 888  10 💤  - 5   8 ❌ + 8  22 🔥 +22 
1 018 runs   - 875  950 ✅  - 928  10 💤  - 5  33 ❌ +33  25 🔥 +25 

For more details on these failures and errors, see this check.

Results for commit 3ab1375. ± Comparison against base commit c2e3fb9.

This pull request removes 909 and adds 46 tests. Note that renamed tests count towards both.
Chrome ‑ Acceptance | Code patches tests: LLM mode event controls auto-apply of code patches with timestamp checking
Chrome ‑ Acceptance | Code patches tests: action bar disappears when "Cancel" button is clicked
Chrome ‑ Acceptance | Code patches tests: automatic Accept All spinner appears in Act mode for multiple patches
Chrome ‑ Acceptance | Code patches tests: can create new files using the search/replace block
Chrome ‑ Acceptance | Code patches tests: can patch code
Chrome ‑ Acceptance | Code patches tests: can patch code and execute command using "Accept All" button
Chrome ‑ Acceptance | Code patches tests: can restore content of a patched file to its original state
Chrome ‑ Acceptance | Code patches tests: does not display the action bar when the streaming is cancelled
Chrome ‑ Acceptance | Code patches tests: empty file shows generating content while streaming a new file patch
Chrome ‑ Acceptance | Code patches tests: empty file shows generating content while waiting for patch acceptance
…
Chrome ‑ Acceptance | code submode | create-file tests > when user has permissions to both test realms: can upload a file via the New menu
Chrome ‑ Acceptance | code submode | create-file tests > when user has permissions to both test realms: cancelling upload file picker does not cause errors
Chrome ‑ Acceptance | code submode | create-file tests > when user has permissions to both test realms: new file button has options to create card def, field def, card instance, text files, and upload file
Chrome ‑ Acceptance | code submode | editor tests: text file in writable realm is not read-only
Chrome ‑ Acceptance | code submode | file-tree tests > when the user lacks write permissions: file tree does not show context menu in read-only realm
Chrome ‑ Acceptance | code submode | file-tree tests: can cancel delete from file tree context menu
Chrome ‑ Acceptance | code submode | file-tree tests: can delete a file from file tree context menu
Chrome ‑ Acceptance | code submode | file-tree tests: can delete a file via right-click in file tree
Chrome ‑ Global error: Uncaught Error: Assertion Failed: You attempted to update `loader` on `<LoaderService:ember68105>`, but it had already been used previously in the same computation.  Attempting to update a value after using it in a computation can cause logical errors, infinite revalidation bugs, and performance issues, and is not supported.  `loader` was first used:  FieldComponent   CardContextConsumer     CardCrudFunctionsConsumer       PermissionsConsumer         DefaultFormatsConsumer           DefaultFormatsProvider             (unknown template-only component)               DynamicElement                 Isolated  Stack trace for the update: at http://localhost:7357/assets/app-gpFxR7J3.js, line 347290  While executing test: Acceptance | code-submode | card playground > error handling: it can clear card-creation error that did not result in new file in the realm 
Chrome ‑ Global error: Uncaught Error: Assertion Failed: You attempted to update `renderError` on `<MockLocalIndexer:ember1355>`, but it had already been used previously in the same computation.  Attempting to update a value after using it in a computation can cause logical errors, infinite revalidation bugs, and performance issues, and is not supported.  `renderError` was first used:  FieldComponent   CardContextConsumer     CardCrudFunctionsConsumer       PermissionsConsumer         DefaultFormatsConsumer           DefaultFormatsProvider             (unknown template-only component)               DynamicElement                 DefaultCardDefTemplate  Stack trace for the update: at http://localhost:7357/assets/app-gpFxR7J3.js, line 347290  After execution of test: Acceptance | operator mode tests: visiting operator mode 
…

♻️ This comment has been updated with latest results.

@github-actions
Copy link

github-actions bot commented Feb 19, 2026

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