Skip to content

Consume boxel-ui directly#5471

Open
ef4 wants to merge 4 commits into
mainfrom
unbuilt-boxel-ui
Open

Consume boxel-ui directly#5471
ef4 wants to merge 4 commits into
mainfrom
unbuilt-boxel-ui

Conversation

@ef4

@ef4 ef4 commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

This removes the build step in boxel-ui.

To keep the public import paths simple despite the constraint that package.json exports can't do extension search, I opted to make all the publicly importable modules use .gts extension. Since it's a superset of .ts there's no harm in using it even in a file that has no templates. The way the exports rules are written, an import ending in an explicit .css will map to .css, and anything else will get an implied .gts.

The test-app needed to gain basic infrastructure for glimmer-scoped-css- and ember-concurrency, since those are no longer compiled away in boxel-ui's own build. This is consistent with the support that host already has anyway.

This PR keeps the build scripts but makes them into no-ops, since they're touched by a lot of the CI infrastructure. A followup PR can eliminate them.

Also, the rollup dependencies and config in boxel-ui could get eliminated after this PR lands.

This removes the build step in boxel-ui.

To keep the public import paths simple despite the constraint that package.json exports can't do extension search, I opted to make all the publicly importable modules use `.gts` extension. Since it's a superset of `.ts` there's no harm in using it even in a file that has no templates. The way the exports rules are written, an import ending in an explicit `.css` will map to `.css`, and anything else will get an implied `.gts`.

The test-app needed to gain basic infrastructure for glimmer-scoped-css- and ember-concurrency, since those are no longer compiled away in boxel-ui's own build. This is consistent with the support that host already has anyway.

This PR keeps the build scripts but makes them into no-ops, since they're touched by a lot of the CI infrastructure. A followup PR can eliminate them.

Also, the rollup dependencies and config in boxel-ui could get eliminated after this PR lands.
@ef4 ef4 mentioned this pull request Jul 10, 2026
3 tasks
@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Preview deployments

Host Test Results

    1 files      1 suites   2h 57m 6s ⏱️
3 454 tests 3 439 ✅ 15 💤 0 ❌
3 473 runs  3 458 ✅ 15 💤 0 ❌

Results for commit f3d57a3.

Realm Server Test Results

    1 files  ±    0      1 suites  +1   10m 53s ⏱️ + 10m 53s
1 814 tests +1 814  1 814 ✅ +1 814  0 💤 ±0  0 ❌ ±0 
1 893 runs  +1 893  1 893 ✅ +1 893  0 💤 ±0  0 ❌ ±0 

Results for commit f3d57a3. ± Comparison against earlier commit 184ca7a.

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.

2 participants