-
Notifications
You must be signed in to change notification settings - Fork 5k
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
web3 postinstall script modifies files in another package #3717
Comments
@abacabadabacaba this is extremely concerning. Thank you for reporting this. I'm not seeing any post-install scripts, do you mind sharing how you discovered this? I've dumped my install log, and if you could do the same that would be great. I did so with the following steps.
|
See also: PR #3136. |
Hmmm interesting ok. I'm going to look into it this week. |
This has been merged |
Closed
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found that postinstall script in web3 package attempts to modify files in an unrelated package, @angular-devkit/build-angular. I believe this to be an abuse of NPM script functionality. Packages should not modify files that they don't own without the user's explicit request.
There are other problems with this behavior:
../../node_modules/@angular-devkit
. This may not be true, as NPM may use a different directory structure in case of name conflicts. See npm-folders documentation page for details.If the modifications are needed, they should be performed by a script that the user needs to run explicitly, perhaps as part of their build process.
Expected behavior
Installing web3 package doesn't mess with other packages.
Actual behavior
Installing web3 package attempts to modify a different package.
Steps to reproduce the behavior
Logs
Environment
The text was updated successfully, but these errors were encountered: