This warning now shows up at all times when in an Angular version 14 environment. This was also found in the regular InfoMapper application as well. There might be a way to put a band-aid on it, but it seems hacky and involves adding more properties to the angular.json file, which I don't like. The Stack Overflow can be found here.
According to multiple sources, it is a bug in the Critters library, and is actively being looked into now. So before I go adding to configuration files, I'll leave this issue open for now and hope they resolve this in the next month or two. The issue can be found here, with a prominent Angular developer chipping in as well (since the @angular-devkit is what relies on said package).
This warning now shows up at all times when in an Angular version 14 environment. This was also found in the regular InfoMapper application as well. There might be a way to put a band-aid on it, but it seems hacky and involves adding more properties to the
angular.json
file, which I don't like. The Stack Overflow can be found here.According to multiple sources, it is a bug in the Critters library, and is actively being looked into now. So before I go adding to configuration files, I'll leave this issue open for now and hope they resolve this in the next month or two. The issue can be found here, with a prominent Angular developer chipping in as well (since the @angular-devkit is what relies on said package).