Read the statement by Michael Teeuw here.
Installing on a Pi Zero
-
@liamangelus git clone the mm repo from GitHub.
Then edit the package.json file and change the number behind electron to the string mentioned above “^2.0.0”Then follow the manual install steps from the readme
-
After editing the electron version in the package.json as ^ 2.0.0, I will apply the other steps in the same way. If I encounter a problem I would like to help you again. Thanx a lot.
-
That works for me. Thanks!
-
Again the same problem when updating to 2.8.0 version
-
@qu1que yes, sadly the electron folks have not provided updates for pi zero
-
looks like changing the electron version to “^2.0.0” isn;t working anymore as it tries to intsall 1.8.0 and it gets the following error. Any idea why it isn’t looking for the version in the package.json file? thanks!
“Error: Failed to find Electron v1.8.0 for linux-armv6l at https://github.com/electron/electron/releases/download/v1.8.0/chromedriver-v1.8.0-linux-armv6l.zip”
-
Solve it like this: “npm install --arch=armv7l”
-
-
@qu1que
Yes, I just update installation command by --arch argument, and MM installs w/o errors. -
@InfiProj is there a command u could use to tell this is a zero, So I could update the installer?
Thanks
-
@sdetweil
In Linux we can ask OS about architecture. “arch” - this command returns CPU architecture. For rpi zero - armv6l, for rpi 3b - armv7l. Maybe that helps you. -
@InfiProj it does. Thx
Not near computer, maybe uname provides info too
-
@sdetweil
“uname -m” - does the same as “arch”,
“uname -p” and “uname -i” says unknown. -
Thanks for the PDF guide/instructions, after a week of tinkering and googling this was the only method I got to work with my Zero (Wish I started with this guide!)
-
@InfiProj thanks… I’ve updated my new test installer to use that info
https://forum.magicmirror.builders/topic/10171/anyone-want-to-try-updated-installer?page=1
my intent is to submit this new installer to replace the project version…
-
I just attempted to install 2.11.0 on a Pi0 W, I got the following error running
npm install:npm install npm ERR! Cannot read property 'resolve' of undefined npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2020-04-12T20_08_37_082Z-debug.logThe log contains:
0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'install' ] 2 info using npm@6.14.4 3 info using node@v10.20.0 4 verbose npm-session ed148b8dcfcaa591 5 silly install runPreinstallTopLevelLifecycles 6 silly preinstall magicmirror@2.11.0 7 info lifecycle magicmirror@2.11.0~preinstall: magicmirror@2.11.0 8 silly install loadCurrentTree 9 silly install readLocalPackageData 10 timing stage:loadCurrentTree Completed in 897ms 11 silly install loadIdealTree 12 silly install cloneCurrentTreeToIdealTree 13 timing stage:loadIdealTree:cloneCurrentTree Completed in 10ms 14 silly install loadShrinkwrap 15 timing stage:loadIdealTree:loadShrinkwrap Completed in 42390ms 16 silly install loadAllDepsIntoIdealTree 17 silly fetchPackageMetaData error for grunt@latest Cannot read property 'resol ve' of undefined 18 silly fetchPackageMetaData error for grunt-eslint@latest Cannot read property 'resolve' of undefined 19 silly fetchPackageMetaData error for grunt-jsonlint@latest Cannot read property 'resolve' of undefined 20 silly fetchPackageMetaData error for grunt-markdownlint@latest Cannot read property 'resolve' of undefined 21 silly fetchPackageMetaData error for grunt-stylelint@latest Cannot read property 'resolve' of undefined 22 silly fetchPackageMetaData error for grunt-yamllint@latest Cannot read property 'resolve' of undefined 23 silly fetchPackageMetaData error for stylelint@latest Cannot read property 'resolve' of undefined 24 silly fetchPackageMetaData error for stylelint-config-standard@latest Cannot read property 'resolve' of undefined 25 silly fetchPackageMetaData error for time-grunt@latest Cannot read property 'resolve' of undefined 26 silly fetchPackageMetaData error for feedme@latest Cannot read property 'resolve' of undefined 27 silly fetchPackageMetaData error for iconv-lite@latest Cannot read property 'resolve' of undefined 28 silly fetchPackageMetaData error for moment@latest Cannot read property 'resolve' of undefined 29 silly fetchPackageMetaData error for valid-url@latest Cannot read property 'resolve' of undefined 30 silly fetchPackageMetaData error for feedme@latest Cannot read property 'resolve' of undefined 31 silly fetchPackageMetaData error for iconv-lite@latest Cannot read property 'resolve' of undefined 32 silly fetchPackageMetaData error for moment@latest Cannot read property 'resolve' of undefined 33 silly fetchPackageMetaData error for valid-url@latest Cannot read property 'resolve' of undefined 34 timing stage:rollbackFailedOptional Completed in 6ms 35 timing stage:runTopLevelLifecycles Completed in 47409ms 36 silly saveTree magicmirror@2.11.0 36 silly saveTree ├─┬ chai-as-promised@7.1.1 36 silly saveTree │ └── check-error@1.0.2 ... 36 silly saveTree │ └── querystring@0.2.0 36 silly saveTree ├── wdio-dot-reporter@0.0.10 36 silly saveTree └── wgxpath@1.0.0 37 verbose stack TypeError: Cannot read property 'resolve' of undefined 37 verbose stack at regFetch (/usr/local/lib/node_modules/npm/node_modules/n pm-registry-fetch/index.js:88:23) 37 verbose stack at fetchPackument (/usr/local/lib/node_modules/npm/node_mod ules/pacote/lib/fetchers/registry/packument.js:42:10) 37 verbose stack at packument (/usr/local/lib/node_modules/npm/node_modules/ pacote/lib/fetchers/registry/packument.js:20:10) 37 verbose stack at getManifest (/usr/local/lib/node_modules/npm/node_module s/pacote/lib/fetchers/registry/manifest.js:22:10) 37 verbose stack at manifest (/usr/local/lib/node_modules/npm/node_modules/p acote/lib/fetchers/registry/manifest.js:13:10) 37 verbose stack at Object.manifest (/usr/local/lib/node_modules/npm/node_mo dules/pacote/lib/fetchers/registry/index.js:17:12) 37 verbose stack at Object.Fetcher#manifest [as manifest] (/usr/local/lib/no de_modules/npm/node_modules/genfun/lib/genfun.js:15:38) 37 verbose stack at manifest (/usr/local/lib/node_modules/npm/node_modules/p acote/lib/fetch.js:23:18) 37 verbose stack at pinflight (/usr/local/lib/node_modules/npm/node_modules/pacote/manifest.js:24:12) 37 verbose stack at /usr/local/lib/node_modules/npm/node_modules/promiseinflight/inflight.js:29:24 37 verbose stack at Promise._execute (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/debuggability.js:313:9) 37 verbose stack at Promise._resolveFromExecutor (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:488:18) 37 verbose stack at new Promise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:79:10) 37 verbose stack at _inflight (/usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:28:25) 37 verbose stack at /usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:22:14 37 verbose stack at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23) 38 verbose cwd /home/pi/MagicMirror 39 verbose Linux 4.9.35+ 40 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" 41 verbose node v10.20.0 42 verbose npm v6.14.4 43 error Cannot read property 'resolve' of undefined 44 verbose exit [ 1, true ]Any idea where resolve should be set and what is missing?
-
@nigel-daniels i do not know… please use the scripted install from here
https://github.com/sdetweil/MagicMirror_scripts
look at the instructions
also, rename MagicMirror folder out of the way… or erase it… install thinks it is doing for the 1st time.
-
@sdetweil hi, I have everything else set up and don’t really want to change thing, I had configured the PiZero some time ago. I was just reinstalling MM2. I decided I had left it so long since the last up date I just backed up my modules + config and have performed a reinstall. As far as I can tell the script is attempting a full config of the pi0?
-
@nigel-daniels no, just mm
-
@sdetweil looks like the script gets to the same place :(
Installing dependencies ... npm WARN optional SKIPPING OPTIONAL DEPENDENCY: electron@^6.1.7 (node_modules/electron): npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Cannot read property 'resolve' of undefined npm ERR! Cannot read property 'resolve' of undefined npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2020-04-13T15_17_35_327Z-debug.log Unable to install dependencies!The
config.jsononly mentions electron in the optional dependancies so I don’t know where theresolvecomes from. It looks to the the property of somevarthat is not being set.
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