You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do we need to support backwards compatibility with the filename? I would think that is something consumers shouldn't rely on being static.
It is certainly reasonable to support this backwards compatibility, but it does add extra overhead and clutter to out build process. We could remove this in the next major, though just wanted to examine if it is really something we'd consider a breaking change.
The text was updated successfully, but these errors were encountered:
With the Vite in admin stuff, I'm reasonably sure it no longer bothers to look for esnext code in packages (@vsumner can confirm if that's the case now and/or if it is slated to return)
If that's never coming back then perhaps there's a world where polaris stops bothering to create the esnext bundle entirely?
jesstelford
added
v14.0.0
Tracking the work for @shopify/polaris v14.0.0 release
and removed
v13.0.0
Tracking all work for @shopify/polaris-react v13.0.0
labels
Mar 15, 2024
Originally posted by @sam-b-rose in #11340 (review):
The text was updated successfully, but these errors were encountered: