Update:
My guess is this either has to be solved in the nodebb/package.json or in the npm configuration for the two theme modules.
Here is what you get when you try to npm install with the included nodebb/package.json:
npm ERR! notarget No compatible version found: nodebb-theme-vanilla@'>=2.0.19 <3.0.0' npm ERR! notarget ["0.0.1", ... ,"2.0.10","2.0.11","2.0.12","2.0.13","2.0.14","2.0.15","2.0.16","3.0.0","3.0.1"]and if I fix the nodebb-theme-persona version, I get this on the next npm install` right now:
npm ERR! notarget No compatible version found: nodebb-theme-vanilla@'>=2.0.19 <3.0.0' npm ERR! notarget Valid install targets: npm ERR! notarget ["0.0.1",...,"2.0.1","2.0.2","2.0.3","2.0.4","2.0.5","2.0.6","2.0.7","2.0.8","2.0.9","2.0.10","2.0.11","2.0.12","2.0.13","2.0.14","2.0.15","2.0.16","3.0.0","3.0.1"]I was able to fix this by altering my nodebb/package.json from:
"nodebb-theme-persona": "^1.0.24", "nodebb-theme-vanilla": "^2.0.19",to
"nodebb-theme-persona": "^1.0.21", "nodebb-theme-vanilla": "^2.0.16",What is very strange:
npm info nodebb-theme-persona:
Notice the all show up under the time field of , but not under the versions field. I'm fairly sure this is why npm install doesn't find a suitable version of the npm modules / nodebb plugins to install.
Output from npm info nodebb-theme-vanilla:
versions: ... '2.0.10', '2.0.11', '2.0.12', '2.0.13', '2.0.14', '2.0.15', '2.0.16', '3.0.0', '3.0.1' ], time: ... '2.0.16': '2015-07-28T13:34:41.548Z', '2.0.17': '2015-07-29T15:31:44.952Z', '2.0.18': '2015-07-29T16:42:17.123Z', '2.0.19': '2015-07-29T16:58:55.254Z', '2.0.20': '2015-07-30T19:26:37.250Z', '3.0.0': '2015-08-04T14:32:22.192Z', '3.0.1': '2015-08-04T14:49:45.409Z' },Notice the npm install errors come from versions missing, but there are keys in the time dict.
