Hey there, we are currently migrating all our ui_extensions to use Polaris web components, Preact and API version 2026-07. The latter two areas didn’t face any major hiccups, but we have a couple extensions that rely on UI components that aren’t currently possible to build using the latest Polaris web components. With regards to migration, I had a few questions:
- What happens to extensions if we don’t migrate them? Do they still work as is for merchants?
- What if we migrate other
ui_extensionsbut keep the one’s that rely on old UI components as is? Will updates to already migrated extensions be blocked because some other extensions weren’t migrated?
To add more context, here’s what our current extensions rely on which isn’t possible with the move to Polaris web components:
- Controllable Popovers: We have an extension that requires a search box + results in a popover (similar to ComboBox) and
s-popovercannot achieve the same results as it’s older React-based version.s-popoverrenders on top of the activator, and we need it at the bottom. It should also be treated like a form, so the user can go from search to selecting an item from the results popover via keyboard navigation. These two aren’t possible withs-popover. - Font size: Earlier, we had the ability to choose the font size of a text component using tokens. In Polaris web components, that’s gone. It now relies on semantics completely. We have an editor that let’s our users customize how the extension looks like on their customer accounts surface and if we switch to using web components, we won’t be able to provide that.
We are willing to wait if there’s a potential release down the line the fixes our issues, but we don’t want that to happen at the cost of blocking updates to our other extensions that were migrated successfully. Out of the two points, the 1st is crucial. The entire feature depends on it. I hope I didn’t break any community rules, this is my first post here.