ente/web/packages/next
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
..
.eslintrc.js Move into web/ 2024-03-01 12:21:07 +05:30
hello.ts Move into web/ 2024-03-01 12:21:07 +05:30
next.config.base.js [web] Remove Sentry 2024-03-12 13:24:33 +05:30
package.json Move into web/ 2024-03-01 12:21:07 +05:30
README.md Move into web/ 2024-03-01 12:21:07 +05:30
tsconfig.json Move into web/ 2024-03-01 12:21:07 +05:30

@/next

Like @/ui, but for things that require Next.

Packaging

This (internal) package exports a React TypeScript library. We rely on the importing project to transpile and bundle it.