…just minutes ago, I managed to get back on track by using an elevated prompt outside vs-code, surfed to my project, asked for ‘nvm-w’ decided to upgrade node to latest version 16.9.1 (just from lack of other ideas) knowing that also the latest npm comes along, I gave that a try. With version 16 it did install npm as -g. After it succeeded, it asked to perform a minor upgrade for npm -g. It kept working, reinstalled firebase tools -g, tried to execute ‘npm run start’’ and … yes, an app again! Thereafter, trying to retrieve data via gcloud, had to perform an update on gcloud as well, as a final step importing data with ‘firebase emulators:start --import ./seed’ and again yes, success, back to browser and … luckyme, data is shown again, back on track, pfff!. The last step did notify me about the local projects was using ‘engine:14’ whereas global runs on 16., a minor fix… It was already on my mind this could may be, be another problem… Learning fact, it seems to be important to be aware of the fact which package needs to be installed with -g and it needs to be down knowing (or setting to be on the right node version and performing these steps outside vs-code on an elevated terminal. I though I had a pretty good idea when to do local or -g, I am not so sure anymore, needs to dive in to it once more! Have fun!