MetaMask / MetaMask/metamask-mobile
update @lavamoat/react-native-lockdown
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
### What is this about?
Patch to `@lavamoat/react-native-lockdown` added on https://github.com/MetaMask/metamask-mobile/pull/19736 to fix error stack traces.
Upcoming SES release is expected to include improvements on this area.
Watch [LavaMoat release page](https://github.com/LavaMoat/LavaMoat/releases?q=react-native-lockdown&expanded=true) for a new release of `@lavamoat/react-native-lockdown` > 0.1.0
### Scenario
_No response_
### Design
_No response_
### Technical Details
_No response_
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### Stakeholder review needed before the work gets merged
- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
_No response_
Contributor guide
Research direction
Review MetaMask pull request 19736 and the LavaMoat release page for a new @lavamoat/react-native-lockdown release newer than 0.1.0. No file or test is named; the work is complete when the dependency uses the newer release containing the error-stack-trace fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100