fix(*): drop chat re-export from root entry of public API #16602
+0
−1
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.
Fixes #16601
Chat is still accessible through its
'igniteui-angular/chat'entry as intended, just not through the root entry re-exports (that cover backwards compatibility) as it relies on optional dependencies.Note: Also tried with explicit exports to see it if we can keep in root like
since star exports still need to resolve to figure out the module which could mess some shaking, but nope. Haven't dug too deep, guessing there's a bundle pass that doesn't do shaking first or it doesn't work that way at all.
Additional information (check all that apply):
Checklist:
feature/README.MDupdates for the feature docsREADME.MDCHANGELOG.MDupdates for newly added functionalityng updatemigrations for the breaking changes (migrations guidelines)