From 9f0b40722ae67603385fabdc5549d2699988eea3 Mon Sep 17 00:00:00 2001
From: Joost Huizinga <jhu@woodwing.com>
Date: Tue, 31 May 2022 16:13:44 +0200
Subject: [PATCH] fix: don't import BrowserAnimationsModule in a library

Leave importing BrowserAnimationsModule to the application or else lazy loaded routes will error that BrowserModule has already been loaded.
---
 src/lib/simple-notifications.module.ts | 2 --
 1 file changed, 2 deletions(-)

diff --git a/src/lib/simple-notifications.module.ts b/src/lib/simple-notifications.module.ts
index 609e082..b960872 100644
--- a/src/lib/simple-notifications.module.ts
+++ b/src/lib/simple-notifications.module.ts
@@ -5,7 +5,6 @@ import { SimpleNotificationsComponent } from './components/simple-notifications/
 import { DEFAULT_OPTIONS } from './consts/default-options.const';
 import { Options } from './interfaces/options.type';
 import { NotificationsService } from './services/notifications.service';
-import { BrowserAnimationsModule } from '@angular/platform-browser/animations';
 
 export const OPTIONS = new InjectionToken<Options>('options');
 export function optionsFactory(options) {
@@ -18,7 +17,6 @@ export function optionsFactory(options) {
 @NgModule({
   imports: [
     CommonModule,
-    BrowserAnimationsModule,
   ],
   declarations: [
     SimpleNotificationsComponent,