Read the statement by Michael Teeuw here.
v2.18.0 update gave black screen, then nothing.
-
@richard238 It seems your versions of npm and node might be older than the required versions. run the following
node -v npm -v -
$ node -v v10.24.1 $ npm -v 7.24.2 -
@richard238 You want to update both first.
-
-
@richard238 Just google update npm and update node. Once those are updated then you can do the rest. Uninstall mysql and run npm install in the MMM-MysqlQuery folder. Hopefully that will resolve the issues.
-
Ok, step one completed and looking much more up-to-date:
pi@magicmirror:~ $ npm -v 8.3.0 pi@magicmirror:~ $ node -v v17.3.0 -
And step two:
pi@magicmirror:~/MagicMirror $ npm uninstall mysql up to date, audited 758 packages in 10s 66 packages are looking for funding run `npm fund` for details found 0 vulnerabilitiespi@magicmirror:~/MagicMirror $ cd modules/MMM-MysqlQuery pi@magicmirror:~/MagicMirror/modules/MMM-MysqlQuery $ npm install npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: mmm-mysqlquery@1.0.0 npm ERR! Found: stylelint@8.4.0 npm ERR! node_modules/stylelint npm ERR! dev stylelint@"^8.3.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer stylelint@"^14.0.0" from grunt-stylelint@0.17.0 npm ERR! node_modules/grunt-stylelint npm ERR! dev grunt-stylelint@"latest" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /home/pi/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2022-01-06T12_51_27_088Z-debug-0.log pi@magicmirror:~/MagicMirror/modules/MMM-MysqlQuery $ -
@richard238 can you check if package-lock.json exist. if it does delete it
rm package-lock.jsonthen try again. Also, did you do the uninstall in the MagicMirror folder first? -
did you do the uninstall in the MagicMirror folder first?
Yes, I did.pi@magicmirror:~ $ sudo rm package-lock.json pi@magicmirror:~ $ cd ~/MagicMirror pi@magicmirror:~/MagicMirror $ cd modules/MMM-MysqlQuery pi@magicmirror:~/MagicMirror/modules/MMM-MysqlQuery $ npm install npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: mmm-mysqlquery@1.0.0 npm ERR! Found: stylelint@8.4.0 npm ERR! node_modules/stylelint npm ERR! dev stylelint@"^8.3.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer stylelint@"^14.0.0" from grunt-stylelint@0.17.0 npm ERR! node_modules/grunt-stylelint npm ERR! dev grunt-stylelint@"latest" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /home/pi/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2022-01-06T13_37_32_112Z-debug-0.log pi@magicmirror:~/MagicMirror/modules/MMM-MysqlQuery $ -
@richard238 seems like styleint is giving issues, Can you just try and install mysql and see if that resolves your issue?
-
Install mysql - how and where?
Apologies for the detail request, but having got this far, I don’t want to break anything else.
Thank you.
-
@richard238 In the MMM-MysqlQuery folder,
npm i mysql -
pi@magicmirror:~/MagicMirror/modules/MMM-MysqlQuery $ npm i mysql npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: mmm-mysqlquery@1.0.0 npm ERR! Found: stylelint@8.4.0 npm ERR! node_modules/stylelint npm ERR! dev stylelint@"^8.3.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer stylelint@"^14.0.0" from grunt-stylelint@0.17.0 npm ERR! node_modules/grunt-stylelint npm ERR! dev grunt-stylelint@"latest" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /home/pi/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2022-01-06T14_02_53_804Z-debug-0.log pi@magicmirror:~/MagicMirror/modules/MMM-MysqlQuery $ -
@richard238 run
npm i mysql --forceThe stylint is a dev dependency. -
Looking better…
pi@magicmirror:~/MagicMirror/modules/MMM-MysqlQuery $ npm i mysql --force npm WARN using --force Recommended protections disabled. npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: grunt-stylelint@0.17.0 npm WARN Found: stylelint@8.4.0 npm WARN node_modules/stylelint npm WARN dev stylelint@"^8.3.0" from the root project npm WARN npm WARN Could not resolve dependency: npm WARN peer stylelint@"^14.0.0" from grunt-stylelint@0.17.0 npm WARN node_modules/grunt-stylelint npm WARN dev grunt-stylelint@"latest" from the root project npm WARN npm WARN Conflicting peer dependency: stylelint@14.2.0 npm WARN node_modules/stylelint npm WARN peer stylelint@"^14.0.0" from grunt-stylelint@0.17.0 npm WARN node_modules/grunt-stylelint npm WARN dev grunt-stylelint@"latest" from the root project npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: stylelint-config-standard@24.0.0 npm WARN Found: stylelint@8.4.0 npm WARN node_modules/stylelint npm WARN dev stylelint@"^8.3.0" from the root project npm WARN npm WARN Could not resolve dependency: npm WARN peer stylelint@"^14.0.0" from stylelint-config-standard@24.0.0 npm WARN node_modules/stylelint-config-standard npm WARN dev stylelint-config-standard@"latest" from the root project npm WARN npm WARN Conflicting peer dependency: stylelint@14.2.0 npm WARN node_modules/stylelint npm WARN peer stylelint@"^14.0.0" from stylelint-config-standard@24.0.0 npm WARN node_modules/stylelint-config-standard npm WARN dev stylelint-config-standard@"latest" from the root project npm WARN ERESOLVE overriding peer dependency npm WARN deprecated time-grunt@2.0.0: Deprecated because Grunt is practically unmaintained. Move on to something better. This package will continue to work with Grunt v1, but it will not receive any updates. npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 added 606 packages, and audited 1043 packages in 3m 49 packages are looking for funding run `npm fund` for details 29 vulnerabilities (1 low, 17 moderate, 11 high) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. pi@magicmirror:~/MagicMirror/modules/MMM-MysqlQuery $ -
@mumblebaj why my install script does npm install --only=prod
to remove the dev dependencies -
@sdetweil :thumbs_up:
-
What are “dev dependencies” to the uninitiated?
-
@richard238 there are dependencies
things needed to RUN
and dev dependencies,
things needed to DEVELOP for existing or new function
things like syntax checkers, format checkers, test cases, … 99% of users don’t need that stuff on their disc
in the package.json are two lists of dependencies
“devDependencies”: {
“dependencies”: {unless u specify only runtime (production) , you get both …
-
Still no MM though. Status says online, but it’s not launching MM.
I’ll reboot, because, why not…pi@magicmirror:~/MagicMirror $ pm2 start MagicMirror [PM2] Applying action restartProcessId on app [MagicMirror](ids: [ 0 ]) [PM2] [MagicMirror](0) ✓ [PM2] Process successfully started ┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐ │ id │ name │ mode │ ↺ │ status │ cpu │ memory │ ├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤ │ 0 │ MagicMirror │ fork │ 0 │ online │ 0% │ 2.6mb │ └────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘ pi@magicmirror:~/MagicMirror $
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login