This PR adds Sentry to allow for error-tracking. You can see the first commit doing that ccea18cce4eae31b4ee449bb9e2c96f299d87601
The second commit e25070acbe20ec5803bd927e581885724fb7f080 adds the sentry domains to the allow list in the security headers. For testing it locally (which I Was unable to do before), I updated the format so the headers are defined in a serve.json file. This way, I found the way I was setting the headers for using an allowlist to download/fetch from was incorrect, so I also fixed that. The .htaccess is now generated from that file as well (so we generate the serve.json file for hosting locally using serve, and the .htaccess for hostinger). A note you will see in that commit is that we had to hardcode the list of RPC URLs, due to the difficulty in retrieving them from hemi-viem mixing ESM and CJS files
Description
This PR adds Sentry to allow for error-tracking. You can see the first commit doing that ccea18cce4eae31b4ee449bb9e2c96f299d87601
The second commit e25070acbe20ec5803bd927e581885724fb7f080 adds the sentry domains to the allow list in the security headers. For testing it locally (which I Was unable to do before), I updated the format so the headers are defined in a serve.json file. This way, I found the way I was setting the headers for using an allowlist to download/fetch from was incorrect, so I also fixed that. The
.htaccessis now generated from that file as well (so we generate theserve.jsonfile for hosting locally usingserve, and the.htaccessforhostinger). A note you will see in that commit is that we had to hardcode the list of RPC URLs, due to the difficulty in retrieving them fromhemi-viemmixing ESM and CJS filesRelated issue(s)
Closes #553 Related to #617
Checklist