@sdetweil thanks for the support, that fixed it!
It looks like npm was broken. I removed node and npm then installed node v10.20.1 and things seem to be working again. Running npm install --only=prod let the install run without getting upset about electron!
@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.json only mentions electron in the optional dependancies so I don’t know where the resolve comes from. It looks to the the property of some var that is not being set.
@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?
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.log
The 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?
Hi, I have not been able to work on these modules as a full time role has limited my time considerably. To make tweaks I recommend forking the repo in git hub.
Just in case there are any super early adopters, I added a fix to stop trains from disappearing if I did not get back a response from a particular vehicle. The times are now cached if this happens so the old time is used until I get an update or they become outdated by the response time.
This module shows arrival times for a VTA light rail stop on the Santa Clara Valley Transportation Authority system. Useful if you’re in the South Bay and running for a train :)
You can get this module from HERE! Enjoy.
@twosquirrels ok I have made the changes, so try an update. The blanks should now display the headline status. Sadly the FAA’s documentation is somewhat opaque and does not seem to totally match what I actually get from the API so there may be one or two cases where the word ‘undefined’ crops up rather than a time for an actual delay. If you see that just drop me a line and let me know what the status and text was and I’ll try and figure out what’s going on.
@twosquirrels sorry for the delay in getting to this, I just got back from some travels. It looks like the FAA have made more changes than I realized. Next to the airports code (in the red boxes) should be a short status indicator, e.g. ‘Ok’, ‘Delays’, ‘Closed’, etc. Then in the line below (which is showing) should be a brief line of detail to give a bit more detail on the status, especially if there is a delay.
I have just migrated this to the WeatherBit API as Wunderground are cancelling the free service 😞 This forces an update of the module and a new config! I’ve updated the read me in GitHub, so please take a look.
I have just migrated this to the WeatherBit API as Wunderground are cancelling the free service :( This forces an update of the module and a new config! I’ve updated the read me in GitHub, so please take a look.
@twosquirrels I’m so sorry. Fortunately I got it right in the git-hub docs!!
@fwood04 hi, you may be seeing errors for this module, the FAA changed stuff and broke the module, I’ve just fixed it so you should be good to update.
@twosquirrels you may be seeing that the MMM-FAA-Delay module is broken, the FAA changed their code and did not let anyone know or put a proxy/web forward in place :( I have updated the code and added a flag displayWeather to the config so that when you update you don’t have to go in and hack the new code again.
The FAA have update their API and as a result broke this module. There is an updated version now in the git repository. This update has two features:
On your magic mirror go into the MMM-FAA-Delay directory in the modules and run the following commands:
git pull
npm install
This should update the MMM-FAA-Delay code then update it’s dependancies.
@twosquirrels Glad you sorted it out. I figured the weather is useful if you are monitoring airports some distance away but if you live close to the one you track then I can see it’s redundant information.
@MattSharp Hi, from what you describe the error is happening because the node_helper is not getting a response to the call to get the weather status in the first place. That’s where it expect the simpleforcast to be a part of the response. Can you post a version of your config to verify the call is happening ok?
@rak I’m also seeing this issue, I have entries showing on added in the calendar that are no longer part of the news feed online. It seems it’s ‘filling up’ then not refreshing :(
@soqueen sorry I thought the site supported PMs, my bad. Looking at the config you have you have the tube status set to show across the bottom of the screen:
position: 'bottom_bar',
If you move it to show in something like 'bottom_center' then it will restrict the width of the module. Check out the MM2 Read Me for the valid location settings. Hopefully this will correct the issue you are seeing, let me know if it remains a problem.
@soqueen probably best to send me he whole thing just in case it’s an interaction thing, just remove any private api keys and any personal urls (e.g. calendar).