@Jopyth maybe something like alias

{
  module: "modulename",
  alias: "fancymodule",
  ...
}

then check if alias exists if not display normal module name

@schlachtkreuzer6

MMM-Anti-Screen-Burn-In.css

.MMM-Anti-Screen-Burn-In {
    margin: 55px 55px 65px 65px; /*this would shift it 5 pixels higher and 5 pixels to the right side than the standard of 60px on each side*/
}

MMM-Anti-Screen-Burn-In.js

start: function(){
    setInterval(() => {
        document.querySelector("body").classList.toggle("MMM-Anti-Screen-Burn-In");
    }, 6 * 60 * 60 * 1000); // every 6 hours
},

getStyles: function(){
    return ["MMM-Anti-Screen-Burn-In.css"];
}

@shgmongohh [card:SamLewis0602/MMM-Traffic]

@darkeagl105 it’s done from the api after the first matchday this should be fixed automatically

@Knox

{
			module: "helloworld",
			position: "top_left",
			config: {
				text: "<img src='path_or_link_to_your_image'>"
			}
		}

@PointPubMedia

[card:fewieden/MMM-syslog-slave]

@bibi the boot screen is replaced in the newest version if you are using the new raspbian version which is using PIXEL

@andrewchumchal create a package.json file with npm init fill out the fields, after that type npm install --save DEPENDENCY then the dependencie gets saved into the package.json file, when you provide the package.json file with your module the users have to type npm install and all dependencies which are stored in package.json automatically getting installed

[card:fewieden/MMM-NFL]

@geeflaxx there must be something wrong with your whole setup. i would personally go and do it again with this instructions https://forum.magicmirror.builders/topic/236/complete-setup-tutorial