forked from epicweb-dev/epic-stack
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add decision document on source maps
- Loading branch information
1 parent
cc20e62
commit 7d135a3
Showing
2 changed files
with
25 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# Source Maps | ||
|
||
Date: 2023-11-03 | ||
|
||
Status: accepted | ||
|
||
## Context | ||
|
||
Read [016-source-maps](016-source-maps.md) to come up to speed on the context. | ||
|
||
Because of our built-in sentry support, we need to generate source maps, but we | ||
do not necessarily need to ship source maps to the client. Despite the arguments | ||
made in the original source map decision document, the benefit of shipping | ||
source maps over not shipping them is reduced thanks to Sentry. And the dangers | ||
are still present. | ||
|
||
## Decision | ||
|
||
Delete source maps after they've been uploaded to Sentry. | ||
|
||
## Consequences | ||
|
||
This will mean debugging a production application in the client will be really | ||
hard, but with Sentry properly configured it should definitely not be a problem. |