fix npm audit vulnerabilities using resolutions #183
Conversation
|
|
|
Backend code coverage report for PR #183 |
|
Frontend code coverage report for PR #183 |
|
Levitate is-compatible report: 🔍 Resolving @grafana/data@latest... 🔬 Checking compatibility between ./src/module.ts and @grafana/data@9.4.7... 🔬 Checking compatibility between ./src/module.ts and @grafana/ui@9.4.7... 🔬 Checking compatibility between ./src/module.ts and @grafana/runtime@9.4.7... 🔬 Checking compatibility between ./src/module.ts and @grafana/e2e-selectors@9.4.7... ✔️ ./src/module.ts appears to be compatible with @grafana/data,@grafana/ui,@grafana/runtime,@grafana/e2e-selectors |
What this PR does / why we need it:
Which issue(s) this PR fixes:
Our internal security team noted that we have potential vulnerabilities in our devDependencies. These stem from nested dependencies in @grafana and @iot-app-kit package dependencies.
For most of the vulnerabilities, they were patched in very similar versions to what's already in the dependency chain, so this shouldn't cause much of an issue.
For these 2 dependencies, there was a significant shift in Major version, but from testing doesn't seem to impact the build of the customer application, so may appear when we run our automated tests, submitting this PR to find out.
Fixes #
Special notes for your reviewer: