You might need more version resolutions depending on your dependency, you can check them with yarn why @metamask/eth-snap-keyring
Then, run some actions (using the e2e dapp for example) and check logs of your extension (see the screenshots for an example).
Note
For now we do log every Snap requests (and only the requestId in case of failure). I thought that "masking" some properties would be great (using superstruct), however the Snap controller already logs the entire request object, so I guess this is "ok".
You can check that by filtering the logs in your console with metamask:snaps:snaps-controllers
Description
This uses the same logging mechanism than the extension (using
@metamask/utilslogging).You can configure the logger using the
DEBUG"env variable" from your.metamaskrc. Every MetaMask logs are prefixed bymetamask:.In our case, the log prefix would be:
metamask:eth-snap-keyring.Screenshots
Manual testing
Add this resolution to your extension's
package.json:Then, run some actions (using the e2e dapp for example) and check logs of your extension (see the screenshots for an example).
Note
For now we do log every Snap requests (and only the
requestIdin case of failure). I thought that "masking" some properties would be great (usingsuperstruct), however the Snap controller already logs the entire request object, so I guess this is "ok".