- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 205
 
feat(sdk): upgrade @metamask/providers to ^18.3.1 #1199
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
Conversation
| 
          
 New dependencies detected. Learn more about Socket for GitHub ↗︎ 
  | 
    
| 
           👍 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.  | 
    
| 
           @SocketSecurity ignore npm/[email protected]  | 
    
          Codecov ReportAll modified and coverable lines are covered by tests ✅ 
 Additional details and impacted files@@           Coverage Diff           @@
##             main    #1199   +/-   ##
=======================================
  Coverage   74.06%   74.06%           
=======================================
  Files         182      182           
  Lines        4350     4350           
  Branches     1066     1066           
=======================================
  Hits         3222     3222           
  Misses       1128     1128           ☔ View full report in Codecov by Sentry.  | 
    
          
 | 
    



Description
This PR updates the
@metamask/providerspackage to version 18.3.1 and externalizes it as a dependency. This change brings important updates to the MetaMask provider handling but requires attention from dApp developers due to potential breaking changes in build configurations.Key Changes
@metamask/providersfrom16.1.0to^18.3.1rollup.config.jsto externalize@metamask/providersBreaking Changes
This update may require dApp developers to update their build configurations, particularly for Vite-based applications. The following changes might be necessary:
For Vite Applications
Add the following configurations to
vite.config.js:Additional Dependencies
Some applications may need to install these dependencies:
{ "dependencies": { "buffer": "^6.0.3", "stream-browserify": "^3.0.0" } }Migration Guide
Testing Instructions
Review Checklist