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
Currently, to ensure that custom CSS is packed in a bundle, the hasStyles configuration must be set to true in the bundle.yaml. This has two shortcomings:
It's not documented anywhere
There should be ways to determine if a runtime.css is present dynamically and include rather than requiring the config option.
I believe rumtime.css should only be present after build if custom css is imported in which case its intended to be used. Assuming that is the case, the option/flag should be able to be removed. At minimum, the config option should be documented.
The text was updated successfully, but these errors were encountered:
Currently, to ensure that custom CSS is packed in a bundle, the hasStyles configuration must be set to
true
in the bundle.yaml. This has two shortcomings:I believe rumtime.css should only be present after build if custom css is imported in which case its intended to be used. Assuming that is the case, the option/flag should be able to be removed. At minimum, the config option should be documented.
The text was updated successfully, but these errors were encountered: