Full calendar does not work when is used in a lazy-loaded module
See original GitHub issueangular 15.0.2 fullcalendar 6.0.0-beta.3
I have tried to use full calendar in a module that is not lazy loaded - it works ok.
But when I use it in a module that is lazy loaded (via routing), then it bails an error:
Error: Providers from the `BrowserModule` have already been loaded. If you need access to common directives such as NgIf and NgFor, import the `CommonModule` instead.
This happens likely, because you are importing BrowserModule, which you should not do. You can import CommonModule.
Issue Analytics
- State:
- Created 10 months ago
- Reactions:14
- Comments:17 (1 by maintainers)
Top Results From Across the Web
Full calendar events Not working in Angular 9 - Stack Overflow
New fullCalendar calendarOptions along with dayClick in it solves the problem. calendarOptions = { height: '100%', fixedWeekCount: false, ...
Read more >Angular — How to solve the Full-calendar module loading issue
How to resolve this error in the full-calendar module? First, let us have a look at what is angular and why the full-calendar...
Read more >Angular - How to solve the Full-calendar module loading issue
I used Angular material to install full-calendar NPM. However, I faced a loading issue and was not able to compile the Angular application....
Read more >Documentation - FullCalendar
Documentation · Getting Started · Overall Display · Views · Date & Time · Events · Resources · International · Third Party.
Read more >Common errors and how to fix them - Mobiscroll Help Center
Solution: Make sure that the Mobiscroll is installed and the MbscModule is loaded correctly in the module. Note: If you are using lazy...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the report. This is now fixed in v6.0.0-beta.4
Please prio! 😃