It’s not that it’s not worth it. It’s just not cleanest solution.
Read the statement by Michael Teeuw here.

Posts
-
RE: Use npm for module installs
-
RE: Use npm for module installs
@paviro Yes,it has to big of an impact on the file structure. This would require a lot of rewriting. (And besides that, it’s extremely ugly :))
-
RE: Use npm for module installs
@paviro Yes, but that doesn’t mean they are in a specific folder. That would mean all modules will be installed in
~/MagicMirror/modules/node_modules/.
- I don’t think that is what we want. -
RE: Use npm for module installs
By the way, when MM2 is stable, it will be available for installation using
npm install magic mirror
. -
RE: Use npm for module installs
The biggest issue is that you can specifically mention where to install modules.
-
RE: performance issues with fx / loading
I suggest you open a topic on the raspberry pi forum as well… Maybe somebody can elaborate on where we have to look for a solution.
-
RE: Fitbit
This is something very MagicMirror Generic. Maybe we should add something about this in the Readme?
-
Releasing stable
Since MagicMirror² is currently only available as a beta, and the ‘old’ version is still the master branch, I was wondering what you guys think should be the point to release v2 as the master branch?