-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix package json #4893
base: main
Are you sure you want to change the base?
Fix package json #4893
Conversation
That package is necessary as a dependency (opposed to a devDependency) because of the way some platforms (like Angular) depend on some types. I forget the exact details, but I’ll see if I can find the related issue and post it here. Why is this causing an audit issue? |
It was related to this issue, which requires the node types for the |
Hamm… Seems quite old issue and should have been resolved by now by respective packages. |
It may be an issue you don’t experience because you either use the browser exports (which removes the IpcProvider) or you use tree-shaking and don’t use the IpcProvider in your code (so the types also get dropped), which is why you won’t encounter this. Or you pull the types in for your own project, which also satisfies the compiler. But the types reference the In the next major version, the IpcProvider will be moved to an extension package, so this goes away. But ethers has to deal with a significant number of projects, so backwards compatibility is a high priority. There is a CI for Can you provide reproduction steps to demonstrate the audit? There are likely other ways to resolve that issue, and I would of course prefer not needing any sort of audit fix. :) |
Ah… For NPM audit, it is straight forward. Just checkout to main branch and do |
Maybe your branch is out of date and there was an issue with an older version? Here is a result of a fresh checkout and install:
|
@types/node
should be added as a devDependency and not code dependency.npm audit fix