Security News
Bun 1.2 Released with 90% Node.js Compatibility and Built-in S3 Object Support
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.
@keepfy/error-extractor
Advanced tools
A package that handles keepfy specific network & graphql errors for apollo clients
This package wraps all our logic around server error messages sent by keepfy backend, it maps network and graphql errors to a known format and dispatch it to sentry if needed.
yarn add @keepfy/error-extractor
When instantiating apollo client, use it on the error handler:
import * as KeepfyErrorExtractor from 'keepfy-error-extractor'
import ApolloClient from 'apollo-client'
// ...
new ApolloClient({
// ...
onError: (error) => {
const extracted = KeepfyErrorExtractor.fromResponse(error)
if(extracted === 'INVALID_TOKEN'){
// do redirect to login emit
}
}
// ...
})
You can optionally send extracted errors to sentry.
import * as KeepfyErrorExtractor from 'keepfy-error-extractor'
import ApolloClient from 'apollo-client'
const sentryForward = KeepfyErrorExtractor.forwardToSentry(Sentry)
// ...
new ApolloClient({
// ...
onError: (error) => {
const extracted = KeepfyErrorExtractor.fromResponse(error)
sentryForward.captureIfNeeded(extracted, error)
if(extracted === 'INVALID_TOKEN'){
// do redirect to login emit
}
}
// ...
})
Errors will be sent if the package decides that is needed,
for example, UNKNOWN_ERROR
are sent to sentry but
EMAIL_NOT_CONFIRMED
are not. You can always put your own
logic around the captureIfNeeded
call to ignore stuff too.
Note: the handler is made for us to be able to identify non mapped errors, so the sentry open issue has the gql operation name, and some details sent by backend, there's no need to send stack traces (for now).
Note 2: we do not depend on a specific sentry package,
instead, we specify an adapter with the common sentry methods
(available at the types file, look for SentryAdapter
), so
if your sentry passed to the forward call doesn't type check,
just write your adapter for it.
The package offers message suggestions (since not everyone will the strings) separated you can easily get a suggestion like this:
import * as KeepfyErrorExtractor from '@keepfy/error-extractor'
import { ApolloError } from 'apollo-client'
const {
type,
message,
title
} = KeepfyErrorExtractor.getSuggestion('UNKNOWN_ERROR')
// or from apollo error response
mutate(...options)
.catch((error: ApolloError) => {
const suggestion = KeepfyErrorExtractor.suggestionFromGraphQLError(error)
// do something with the error .message or .title
})
FAQs
An error extractor package for keepfy frontend apps
The npm package @keepfy/error-extractor receives a total of 24 weekly downloads. As such, @keepfy/error-extractor popularity was classified as not popular.
We found that @keepfy/error-extractor demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.
Security News
Biden's executive order pushes for AI-driven cybersecurity, software supply chain transparency, and stronger protections for federal and open source systems.
Security News
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.