fix: allow fastify to set content-type dynamically
We can set content-type: application/json for specific routes, but
doing so ends up with confusing, over-engineered code.
Instead we should take care when auditing the endpoints.
* test: allow mocking of env vars
Since utils/env is a module, we can mock it to control env vars in
tests. However, it's not compatible with building the server in
setupFilesAfterEnv, so, instead, we can use a utility function to keep
things DRY.
* fix: update type of fastifyTestInstance
* chore: add comment about sts preload
* chore: rename header plugin
* test: add get util + provide origin on request
* feat: add cors headers
* chore: add TODO
* feat(api): add sentry plugin
Apply suggestions from code review
Revert "feat(api): add sentry plugin"
This reverts commit fcde4ee03e9b83e335a6a2bccd490490e9993597.
install sentryNode
WIP: create sentry debug
WIP: find out why use errorhandler isn't typed correct
install sentry
add the deleted sentry code
create sentry plugin
* fix error found through sentry
* Polish sentry plugin
Co-authored-by: Niraj Nandish <nirajnandish@icloud.com>
* duplicate the changes made in the other plugin
* add done to seterrorHandler
* Fix a typo in sentry option
Co-authored-by: Naomi Carrigan <nhcarrigan@gmail.com>
* Stop the dns from running if a DSN wasn't provided
Co-authored-by: Naomi Carrigan <nhcarrigan@gmail.com>
* Polish the function and check the variable value
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* check the dsn dashboard in the env
* export dsn value if it isn't sentrydashboard
Co-authored-by: Naomi Carrigan <nhcarrigan@gmail.com>
* when the value is undefined init errors
* revert the if statement
* throw an error whenever an environment variable is not right
---------
Co-authored-by: Niraj Nandish <nirajnandish@icloud.com>
Co-authored-by: Naomi Carrigan <nhcarrigan@gmail.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* chore: compile TS into /dist
Having the output co-located with the source meant that the js would be
imported by default. Given that we don't recompile on source changes,
this means the server got 'stuck' at the point of compilation and would
only register changes on build.
Also, compiling to a dist directory should make it easier to build when
we want to deploy. That said, the motivation is mostly DX.
* fix: put schema.prisma in the default location
