chore: Fix development peerDependency warnings
#468
Conversation
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring: Next stepsTake a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with |
|
@SocketSecurity ignore npm/[email protected] Looks like the |
|
@SocketSecurity ignore npm/[email protected] New author is known/trusted |
|
@SocketSecurity ignore npm/@lavamoat/[email protected] This is our package |
The `@lavamoat/preinstall-always-fail` package has been added, and the package `eslint-plugin-import` package has been downgraded by a minor version, both to meet `peerDependency` requirements of other development dependencies. Resolves two warnings, no functional changes.
Gudahtt
force-pushed
the
fix-development-peer-dependency-warnings
branch
from
7a85308
to
dee73c7
Compare
The
@lavamoat/preinstall-always-failpackage has been added, and the packageeslint-plugin-importpackage has been downgraded by a minor version, both to meetpeerDependencyrequirements of other development dependencies.The import plugin downgrade resulted in new lint warnings about import order, which were addressed.
Resolves two warnings, no functional changes.