<![CDATA[NPM script to bundle the server and the client]]>I am wondering whether there is a script to bundle the server app and the client app of MM, so that they are minified in 2 to 10 files or more, but not 10.000.
I have just found this discussion, which seems old and closed.

Would you help answering this question?

]]>https://forum.magicmirror.builders/topic/19142/npm-script-to-bundle-the-server-and-the-clientRSS for NodeSat, 16 May 2026 23:22:32 GMTSat, 16 Nov 2024 12:00:55 GMT60<![CDATA[Reply to NPM script to bundle the server and the client on Thu, 03 Jul 2025 11:31:47 GMT]]>@Tammieda i am not the OP and i dont see how this would work.

its been 7 years since the original discussion, and no example has been forthcoming

anyhow the MagicMirror team is not working on this.
anyone else is welcome to experiment and post issues

]]>https://forum.magicmirror.builders/post/127208https://forum.magicmirror.builders/post/127208Thu, 03 Jul 2025 11:31:47 GMT<![CDATA[Reply to NPM script to bundle the server and the client on Thu, 03 Jul 2025 02:04:26 GMT]]>@sdetweil You could try using a build tool like Webpack or Vite to bundle both server and client apps into fewer, optimized files. Have you checked if there’s an existing config or plugin for MM that supports this, or would you need help setting one up from scratch?

]]>https://forum.magicmirror.builders/post/127207https://forum.magicmirror.builders/post/127207Thu, 03 Jul 2025 02:04:26 GMT<![CDATA[Reply to NPM script to bundle the server and the client on Mon, 18 Nov 2024 12:32:49 GMT]]>@SimoneMSR we don’t run on Android. So I’m not sure we are talking about the same thing

MagicMirror is a single page web server. The page is composed of live JavaScript code in multiple modules to dynamically render their little bits of the page at runtime

So you would download the empty MagicMirror project somewhere. Add modules, configure the modules. Test
And distribute that. Or make that the server the client devices connect to using the native device browser, which they would already have

]]>https://forum.magicmirror.builders/post/121382https://forum.magicmirror.builders/post/121382Mon, 18 Nov 2024 12:32:49 GMT<![CDATA[Reply to NPM script to bundle the server and the client on Mon, 18 Nov 2024 10:24:51 GMT]]>@sdetweil Hello Sam,
thanks for the question, that I will answer now. I see your point, but I am working with a company that has several devices, and the deploy can be long.

I would like to fasten the upload of source code into my device. Up to now, the upload can stand for 30minutes or more, and on android, I have to make an additional 30minutes move to the Termux app folders, in order for me to run MM on that device.

Thank you for the help

]]>https://forum.magicmirror.builders/post/121381https://forum.magicmirror.builders/post/121381Mon, 18 Nov 2024 10:24:51 GMT<![CDATA[Reply to NPM script to bundle the server and the client on Mon, 18 Nov 2024 12:17:26 GMT]]>@SimoneMSR why do you want this?
what is the problem you are trying to solve?

we are not trying to make our disk size smaller
nor our memory footprint
nor protecting our ip w minify

how do you do as a bundle and have it extendable/configurable by the user

the vast majority of our runtime code is in handling the placement of content in the dom.
there is a bunch of onetime convert from text to operational data. then trigger each module to do its thing, call us when you have new content

packaging is for distribution for multiple users and ‘minimize’ the number of files sent over the network,
but this is all private network not public, and the amount of data moved over the local network is minuscule as the ui and the app are on the same machine 99% of the time

this wouldn’t affect the sourcing of data by the modules. but again this is a tiny amount of data
used by a single user

]]>https://forum.magicmirror.builders/post/121340https://forum.magicmirror.builders/post/121340Mon, 18 Nov 2024 12:17:26 GMT