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 |
|
New and updated dependency changes detected. Learn more about Socket for GitHub ↗︎
Footnotes |
ec5ed61 to
f3f0281
Compare
Codecov Report
@@ Coverage Diff @@
## main #1519 +/- ##
=======================================
Coverage 95.10% 95.10%
=======================================
Files 218 218
Lines 4960 4965 +5
Branches 763 763
=======================================
+ Hits 4717 4722 +5
Misses 243 243
|
38529ae to
76332f3
Compare
|
@metamaskbot publish-preview |
|
Preview builds have been published. See these instructions for more information about preview builds. Expand for full list of packages and versions. |
2170fa6 to
3b98cc8
Compare
|
@metamaskbot publish-preview |
cd9622e to
6dfbae9
Compare
|
@metamaskbot publish-preview |
|
Preview builds have been published. See these instructions for more information about preview builds. Expand for full list of packages and versions. |
|
I have verified that this works in the MetaMask extension. |
bbc29cd to
a118517
Compare
|
@SocketSecurity ignore-all |
* Build packages as both CJS and ESM * Fix lint issues * Ignore more files in SWC build * Fix build issues * Build everything with SWC * Exclude eval-worker.js from build * Fix snaps-utils entry fields * Update snap shasums * Use latest version of @swc/core * Fix end-to-end tests * Output types to `dist/types` * Build source and types in separate CI job * Fix `files` property in `package.json`s * Fix `snap-controllers` exports field * Remove unused script from snaps-simulator * Remove outDir from examples * Add `./` to `create-snap` fields * Update yarn.lock * Update more fields for consistency * Update Yarn constraints * Update snap shasum
tsc) is still used to generate types (and thus perform type checking).package.jsonnow defines anexportsfield, so that consumers of the libraries can choose the right version for their specific environment.