@luisestrada
I’ll prepare how to customize it soon. I’m on travel abroad now and will return to next week. Plz wait a while. Until then, you can hide it with css.

@brentmatthews
Ah sorry. It was not about you. I had confusing @srobison62 and you.

UPDATE 1.9.0 (2024-09-25)

• customHeader available,.
  Now you can add customHeader for the calendar view instead of module’s default header.

• variable maxEventLines by number of rows
  Every month has a different number of weeks in its calendar, so it was hard to adjust the height of the month view. Now, you can assign the variable maxEventLines by the number of rows. (And additional CSS Selectors related to it was added.)

@srobison62

1. XXX_center is not a good place to use CX3 module. center position too narrow and doesn’t have a fixed width because it is decided by left and right width by calculation. Especially in the vertical screen? Terrible. You may have only around 1000px(considering the gap of margin) width of the vertical screen, and that number should be shared with another region, left and right. Usually, a pretty side region would have over 300px, so your center region will have only 300~400px. It is not enough for 7 days cells of the calendar.
   I recommend bottom_bar.

2. The CX3 module doesn’t handle ICS data directly. You may need the default calendar module as a calendar events provider. You also need to set the `broadcastEvents’- related properties properly.

3. It seems you already did CSS modification; it’s your taste. I’ll not mention about it. Anyway, I cannot agree that the default CSS would be awful at all.
   

This is not a direct answer to the question, but just for your reference.
The fetch API can be executed directly in the browser, not just in a Node.js environment. You can call the fetch API directly in MMM-MyModule.js without needing node_helper.js.

Additionally, since the fetch API works asynchronously, you can manage the responses of two fetch calls as follows:

• If you need to use the response that arrives first, use Promise.race() or Promise.any().
• If you need to wait for both responses to arrive before proceeding, use Promise.all().

Using these methods can help you manage data synchronization more efficiently.