* 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
* feat: npm -> pnpm
This resolves the issues with the gatsby client (gatsby-plugin-pnpm
deals with the fact that gatsby is relying on its own dependencies
being de-duped)
and challenge-editor (which doesn't seem to want to automatically install
codemirror and needed its own eslint config)
* fix: correct mocha path for curriculum tests
* fix: use select workspace with -F not -w
* fix: reorganise packages and restrict hoisting
pnpm works best if the workspaces keep their own dependencies, since
dependencies are not flattened and then what node resolves from a
require is predictable.
@types seem to be a special case and more care is required to prevent
them getting smushed together in the root (hence the .npmrc)
* fix: add types for tools + root
* fix: decouple challenge-auditor from client
* fix: add ui-components types
* fix(client): use the latest types for react 16
* fix: prettify
* fix: prettierignore pnpm-lock
* fix: relax hoisting
Turns out pnpm works just fine with types. I don't know what was going
wrong before, but there are no-longer any type conflicts.
* fix: add @redux-saga/core to fix eslint issue
It seems to only be redux-saga that import/named can't cope with, so it
is probably okay to work around this one.
* chore: add chai to tools/scripts/build
* fix: add store to root for cypress
* fix: allow cypress to download binaries
If we want to keep preventing cypress from downloading binaries, we can
figure out a workaround, but I'm allowing it to ease the transition to
pnpm.
My guess about why this is happening is that npm triggers Cypress's
postinstall script, but pnpm does not (because pnpm install only
installs if necessary, perferring to link)
* chore: re-enable pre/post scripts
* fix: update build scripts for client
Co-authored-by: Shaun Hamilton <shauhami020@gmail.com>
* chore: update engines to use pnpm
* fix: enable choice of (super)block for tests
Only 'nix machines for now.
* chore: pin pnpm to version 7
* chore: remove last npms
Except web + curriculum-server. I'll update them when I start work on
them again.
* fix: lockfile check to catch any package-locks
* fix(action): install pnpm for upcoming tests
* chore: add nodemon to new api
Co-authored-by: Shaun Hamilton <shauhami020@gmail.com>
* feat(next-api): add fastify-auth0-verify plugin
* feat(next-api): add fastify-jwt-authz plugin
* feat(next-api): accept privacy endpoint with scopes support
* fix(next-api): ignore eslint and ts errors
They will be fixed in a future PR when the package with errors has been updated
Co-authored-by: Niraj Nandish <nirajnandish@icloud.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
