Upcoming Release April 1, 2026 , breaking changes, some operational changes

sdetweil

@BKeyport nothing has changed… the config folder holds the same configs
and if there were multiple css files, you had to use env variables or the config parm to name it… , the path would change to config/custom.css or config/cssfile2.css whatever

BKeyport

OK - so currently my CSS folder is:

What gets moved?
(FWIW, I don’t know what the CSS files are other than custom and main)

I’m currently setting the CSS file with customCss: "css/custom3.css", in the config,

I’ll change that to customCss: "config/custom3.css", ?

as far as the launching of the server, it’s bash script is:

cd /home/bkey1970/MagicMirror
export MM_CONFIG_FILE=config/config3.js
export MM_PORT=8082
export ELECTRON_DISABLE_GPU=1
DISPLAY=:0 npm run server

nothing changes, right?

sdetweil

@BKeyport the custom*.css files get moved. All the rest stays.

Correct on your config file change for css file

Correct on your startup file. You are doing run server, so are not affected by the change to npm start

also, technically you don’t need DISPLAY=:0
from this

DISPLAY=:0 npm run server

as the server doesn’t use the UI

mumblebaj

@sdetweil All my modules are working well on the dev branch. 🤞

karsten13

@sdetweil said:

the custom*.css files get moved

no, only css/custom.css and only if the target specified in config.customCss doesn’t exist.

This is the normal setup used by ~95% of the users, we cannot handle every edge case so these users must change it manually.

@BKeyport said:

I’m currently setting the CSS file with customCss: “css/custom3.css”, in the config,

I’ll change that to customCss: “config/custom3.css”, ?

in your setup no file is moved automatically. As you are already using the config.customCss feature you can do the changes before next release by

move all the custom*.css file from css to config
change config.customCss: "config/custom3.css"

sdetweil

@karsten13 good point on the move now

My script would have moved them

Have to add a check for the custom css config option

rkorell

@sdetweil I’ve identified some of current modules (not MY modules) to use moment.js heavily.
Does it make sense to contact their developers proactively or even open an “issue” ?
From my mirror-build the impacted modules are: MMM-Strava, MMM-MyGarbage and MMM-NowPlayingOnSpotify …

With regards to planned weather module changes MMM-CalendarExt3Agenda relies on some weather information but this is handled by notification so it should work…

Warm regards,
Ralf

sdetweil

@rkorell on the moment info, we removed it from calendar. Doesn’t mean your modules have to change.

The weather notification interface did not change. No modules should be impacted

BKeyport

@sdetweil For clarification does that remove moment.js system wide, or is it just that module? Will other modules need to add it to their package.json files?

sdetweil

@BKeyport currently moment and moment-time zone are still included in the base