Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support Angular 14

See original GitHub issue

Checklist

Please mark these items with an [x]

I’ve already searched through existing tickets
Other people will find this feature useful

Feature Description

Support Angular 14

Build fail with Angular 14 RC2 :

./node_modules/@fullcalendar/common/main.css:4:0 - Error: Module parse failed: Unexpected token (4:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| /* classes attached to <body> */
| /* TODO: make fc-event selector work when calender in shadow DOM */
> .fc-not-allowed,
| .fc-not-allowed .fc-event { /* override events' custom cursors */
|   cursor: not-allowed;

./node_modules/@fullcalendar/daygrid/main.css:2:0 - Error: Module parse failed: Unexpected token (2:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| 
> :root {
|   --fc-daygrid-event-dot-width: 8px;
| }

./node_modules/@fullcalendar/list/main.css:2:0 - Error: Module parse failed: Unexpected token (2:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| 
> :root {
|   --fc-list-event-dot-width: 10px;
|   --fc-list-event-hover-bg-color: #f5f5f5;

./node_modules/@fullcalendar/timegrid/main.css:6:0 - Error: Module parse failed: Unexpected token (6:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| */
| 
> .fc-v-event { /* allowed to be top-level */
|   display: block;
|   border: 1px solid #3788d8;

Issue Analytics

State:
Created a year ago
Reactions:22
Comments:12 (1 by maintainers)

Top GitHub Comments

10reactions

sha-Ncommented, Jun 9, 2022

for those who come here like me,

one workaround is to add following to angular.json’s styles array

“styles” : [ … “./node_modules/@fullcalendar/common/main.css”, “./node_modules/@fullcalendar/daygrid/main.css”, “./node_modules/@fullcalendar/timegrid/main.css”, “./node_modules/@fullcalendar/list/main.css”, … ],

3reactions

jcompagnercommented, Jul 12, 2022

why is this problem moved to the fullcalender-angular project when the real problem is really in for example the common module:

https://github.com/fullcalendar/fullcalendar/blob/master/packages/common/src/main.ts#L1

there the main.ts file imports a css file which is not really a fully supporting thing

So how should the fullcalendar-angular subproject fix this?