The installation is fresh, but there was an older version installed before. It seems some stuff was installed globally for the previous version. This may make you correct regarding it reading old configs. I resolved a mismatch by doing a reinstall via npm for the global and local (working dir project) versions. Both are now jsreport 2.0.5. This seems to have taken me past the earlier problem. Thank you :)
Although it may be moot, the startup was not saying which config it was reading (the section I pasted was from the 'start' command being issued until the output halted).
When I went to run 'jsreport start' outside the project dir, it would default to dev.config.json. Once the versions were matched, running 'jsreport start' now reads the jsreport.config.json file. Joy!
I now need to find out why I an getting a recurring/looping
"info: fs store is loading data
debug: fs store sync is triggering reload, because /opt/jsreportapp/data/settings was changed by other process"
Perhaps a reboot is a good idea right now to clear our whatever cobwebs might be in temp or memory.
Thanks for the getting back to me! Its much appreciated... :)