Quoting the reply from here:
There was global confusion yesterday when the colors npm package received a rogue update, causing the weird output. The colors package is currently used by pcf-start v1.10.4 as one of the dependencies of the live-server npm package used to refresh the loaded PCF test harness. More info on the issue is here: github.com/.../317
The package owners have since removed the offending change, so re-running npm install should work, see below.
To recover your PCF controls projects, either:
- pin to a known good version of the colors package:
> npm install -D colors@1.4.0
- or: clear node_modules and rebuild it:
- delete folder node_modules
- delete package-lock.json
- npm install
Note that in the next coming monthly refresh of our PCF tooling (pcf-scripts and pcf-start), we already replaced live-server, although for different reasons: it was the cause of many warnings we all saw when running npm install. The live-server package seems no longer to receive code updates, hence we moved away from it
