@td

• This doesn’t work?

getScripts: function () {
  return [ 
    this.file('node_modules/preact/dist/preact.min.js'), //from this module's directory
  ]
}

• Or you can serve preinstall or postinstall scripts for your module to handle that kind of job (additional install, move/rename files, etc.)

@schwarem said in MMM-CalendarExt3Agenda Only loading a few items.:

@sdetweil

Below is the screenshot. It is loading everything, but not displaying in CalendarExt3. I also noticed in the debug console there was the message below. I don’t know what it means.

Not error, just info. You can ignore it.

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

@mwm341
As described also in the link, mix-blend-mode: different is not a cure-all. In many cases, especially with simple high-contrast background, it will work fine. But with a mid-contrast or too complex background image, it will not work as expected.

@movingfish
To collaborate with GooglCalendar, see this; https://github.com/MMRIZE/MMM-CalendarExt3/wiki/Examples-%26-Tips

@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.
   

@plainbroke

put this into your css/custom.css;

.CX3 .cell {
  display: flex;
  flex-direction: column;
}

.CX3 .cell > div {
  order: 1;
}

.CX3 .cell .cellHeader {
  order: 2;
}

.CX3 .eventContainer {
  bottom: calc(var(--cellHeaderHeight) + var(--cellFooterHeight));
}

@BKeyport
Your DOM might not be rendered yet on “start” imo. I think manipulating DOM after “DOM_OBJECT_CREATED” notification would be safer.

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.

@ZiggidyZ
Good job. CX3 and CX3A use heavy CSS juggling, so it is not so easy for those who have not experienced this kind of work.
The only thing I am worried about is that it seems you may modify the CSS file of each module directly.
All custom CSS things should be performed in /css/custom.css by overriding for future-update-proof.