Looking for package.json in all the wrong places

sdetweil

 npm install --only=prod

playwright is a testing tool for development purposes

if you used my scripted install it would have done the same

see
https://github.com/sdetweil/MagicMirror_scripts

u may have the wrong version of npm which s causing the problem.

mm needs v16

bullseye comes w v12

my script handles the upgrade too

HALPi-Thousand

@sdetweil

I’m still running Buster; tried Bullseye, ran into issues. Decided to wait a few versions. Will your script work with Buster as well, or just Bullseye?

Thanks

sdetweil

@halpi-thousand yes, and Mac, and any linux

HALPi-Thousand

@sdetweil

So, I tried using that install script, ran into a few problems.

First I should mention that I did have a successful install of Magic Mirror at one point recently. Found Mystic Mirror, which apparently includes Alexa, which I want, so I deleted Magic and went to install Mystic, but ran into a bit of trickiness, so I installed Magic (or thought I did) until I could work out what to do with Mystic. And that’s around when I started running into this npm problem. Might have skipped something somewhere or gotten somethign wrong, I really don’t recall.

—edit----
You were about to be wading through a ton of text copied from the Terminal, but I somehow managed to figure out the right thing to google, and realizing that node.js was the first thing it had problems with, found out how to get rid of it. That worked. I did the full Magic Mirror installation again, and it’s happy. Just thought I’d mention the solution here.

I’ll take a swing at using your install scripts in a bit, but for now the main problem is solved. Victory!

sdetweil

@halpi-thousand no need to run my script if u have it.

read this about alexa

https://forum.magicmirror.builders/topic/16069/alexa-implementations-now-more-difficult-and-some-features-will-stop-working