Commit graph

14 commits

Author SHA1 Message Date
Manav Rathi eb4d83749f
Hash 2024-04-25 14:08:03 +05:30
Manav Rathi 34d44f599d
Cleanup 2024-04-24 21:12:56 +05:30
Manav Rathi 1106393045
Inline 2024-04-24 20:54:56 +05:30
Manav Rathi 81c729a405
Inline 2024-04-24 16:18:01 +05:30
Manav Rathi 5b928883a6
Tinker 2024-04-24 11:03:49 +05:30
Manav Rathi 1c9c6d849a
Rework 1 2024-04-22 15:30:48 +05:30
Manav Rathi 14e4205feb
Restructure 2024-04-20 12:16:58 +05:30
Manav Rathi d0b1ff5520
In band signalling 2024-04-20 10:17:51 +05:30
Manav Rathi 4055f02a1d
Cleaner 2024-04-13 08:52:37 +05:30
Manav Rathi 3499e47c88
Tweak 2024-04-13 06:47:43 +05:30
Manav Rathi 49b5bff042
Inline 2024-04-07 10:29:00 +05:30
Manav Rathi 42a59f2fb5
Consolidate and deduplicate 2024-04-05 20:35:22 +05:30
Manav Rathi 70cddfdf0b
[web] Remove Sentry
Sentry has a measurable impact on page load, a metric that I'm keen to
improve. Apparently by default it loses us 8-9 page speed points, though that
can be reduced to 3-4
(https://github.com/getsentry/sentry-javascript/issues/9179).

All of this is doable, but there are bigger tasks to deal with. This is not to
say that Sentry won't be useful again at some point, when we have time to deal
with it better. But right now, we discussed that it's just better to remove
Sentry instead of piling on to the sunk cost.
2024-03-12 13:24:33 +05:30
Manav Rathi e15c7e1642 Move into web/ 2024-03-01 12:21:07 +05:30