Reintroduce container
component as a utility
#14993
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #13129
We're adding back the v3
container
component, this time as a utility. The idea is that we support the defaultcontainer
behavior but we will not have an API to configure this similar to what v3 offered. Instead, the recommended approach is to configure it by creating a custom utility like so:We do have an idea of how to migrate existing JS configuration files to the new
@utility
as part of the interop layer and the codemod. This is going to be a follow-up PR though.Test Plan
We added a unit test but we've also played around with it in the Vite playground. Yep, looks like a
container
:Screen.Recording.2024-11-13.at.17.43.08.mov