feat: add @ngneat/helipopper/config
#166
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.
In this commit, we add a new subpackage called
@ngneat/helipopper/config
.This change is intended to separate configuration logic from UI-related functionality.
The configuration should be imported at the root level, while the UI components should
only be imported when necessary. Previously, importing the library at the root
level (when providing the configuration) caused the bundler to include everything in the
main bundle immediately.
With this approach, the configuration is bundled separately at the root level and
includes only the provider functions.
Additionally, while we had already added a
loader
function, to avoid breaking theprovideTippyConfig
signature, we introduced a separate function calledprovideTippyLoader
,which exclusively accepts a loader function.
The
provideTippyConfig
has been reverted to return a provider (not an environment provider),becuase it might be provided at the component level too.