Skip to content

fix: don't import BrowserAnimationsModule in a library #396

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 31, 2022
Merged

fix: don't import BrowserAnimationsModule in a library #396

merged 1 commit into from
May 31, 2022

Conversation

wwjhu
Copy link
Contributor

@wwjhu wwjhu commented May 31, 2022

Leave importing BrowserAnimationsModule to the application or else lazy loaded routes will error that BrowserModule has already been loaded.

fixes #392

Leave importing BrowserAnimationsModule to the application or else lazy loaded routes will error that BrowserModule has already been loaded.
@flauc flauc merged commit f43694b into flauc:master May 31, 2022
@wwjhu wwjhu deleted the fix-import branch May 31, 2022 14:23
@dc-p8 dc-p8 mentioned this pull request Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

issue with lazy loaded module in angular 13
2 participants