-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
devDeps: upgrade test & lint suite #70
base: main
Are you sure you want to change the base?
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 |
This comment was marked as resolved.
This comment was marked as resolved.
Let's see if they pick up typicode/please-upgrade-node#36 |
This comment was marked as resolved.
This comment was marked as resolved.
Many of these look to be eternal until they're removed from entrypoint packages (cf I'm as much for backwards-compat as the next person but with a network of interconnected micropackages all maintained with this approach underpinning the linting, I have a feeling this can get uncomfortable over time. |
Blocked by MetaMask/eslint-config#290 |
This comment was marked as resolved.
This comment was marked as resolved.
b692a63
to
5af2104
Compare
|
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
new author ok |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the long delay on reviewing this. Obviously we need more work to bring this project up to date with the module template but this is a good start. Good call to delay the JSDoc rules, I agree that this can be its own PR — perhaps we want to remove the dummy comments for now? Otherwise this PR looks good.
This upgrades test and lint packages, bringing in configuration in direction of https://github.com/MetaMask/metamask-module-template/.
Migrating to jest and fixing jsdoc comments left as separate changes. Otherwise updated linting rules have been applied.