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, when creating a package bundle, all meta items in the workspace are included in the final bundle.
However, in the case of developing component packs and possibly other scenarios, meta items that are used in "development" are not required to be included in the "prod" bundle.
For example, if I'm developing a component "Swiper", in order to test my component, I have a view in my workspace that contains the component. This view is strictly for dev/test purposes and not required to be distributed with my bundle. The solution for this currently is one (or more) of the following:
Prior to "final", delete the unnecessary meta items (e.g., view) from the web builder
Mark the meta item private but this still results in it being packaged, just not visible
When developing, have two workspaces - one for the component only and another for a view that uses the component
None of these are ideal or a good developer experience.
Possibly consider a way to configure this in bundle.yaml and/or define a dotignore file.
The text was updated successfully, but these errors were encountered:
Currently, when creating a package bundle, all meta items in the workspace are included in the final bundle.
However, in the case of developing component packs and possibly other scenarios, meta items that are used in "development" are not required to be included in the "prod" bundle.
For example, if I'm developing a component "Swiper", in order to test my component, I have a view in my workspace that contains the component. This view is strictly for dev/test purposes and not required to be distributed with my bundle. The solution for this currently is one (or more) of the following:
None of these are ideal or a good developer experience.
Possibly consider a way to configure this in bundle.yaml and/or define a dotignore file.
The text was updated successfully, but these errors were encountered: