Added

• Add getters for spans. Use the getAction, getNamespace, getError, getTags, getParams, getBreadcrumbs, and getEnvironment methods to access data about the current span. This can be used to make decisions based on the span's properties within decorators or overrides.
• Allow overrides to ignore spans. Within an override function, returning false will cause AppSignal to ignore the span.

Changed

• Ignore spans by message after overrides. This allows overrides to modify error messages before ignoring them, allowing the override to cause the span to be ignored, or to prevent it from being ignored.

Deprecated

• Deprecate @appsignal/core and @appsignal/types packages. Packages depending on these packages should be updated to use @appsignal/javascript instead.

Fixed

• Use returned span in override. Fix an issue where the span returned from an override function was not being used, instead using the original span. This led to confusing behaviour when the override created a new span instead of modifying the original one.

  To avoid breaking existing overrides that rely on modifying the original span without returning it, if the override function does not return a span, the original span will still be used.

View the AppSignal JavaScript javascript v1.6.0 changelog for more information.

Added

• Add support for React 19

View the AppSignal JavaScript react v1.0.29 changelog for more information.

Added

• Add a default action to the Stimulus error handler, based on the current controller. (Thanks to Amiel Martin for their contribution!)

View the AppSignal JavaScript stimulus v1.0.19 changelog for more information.

Added

• Allow custom backtrace sanitization.

  Warning: This is an advanced feature meant for specific use cases. For most use cases, you should not need this functionality. If in doubt, leave matchBacktracePaths unset.

  Using matchBacktracePaths will cause public sourcemap detection to fail. If using matchBacktracePaths, use our private sourcemap API to upload sourcemaps to AppSignal.

  Some applications, such as those running on Electron or React Native environments, emit backtrace lines containing paths relative to the device in which the application is running.

  The unpredictability of these backtrace line paths interferes with the correct functioning of backtrace error grouping, and makes it impossible to upload sourcemaps for these files using our private sourcemap API, as it is not possible to know the expected path beforehand.

  You can set the matchBacktracePaths configuration to a list of one or more regexes, which will be used to attempt to match the relevant section of the backtrace line path.

  For example, suppose you have an Electron application, which your users install at unpredictable locations. Your backtrace line paths may look something like this, with the username changing for each installation:

  Shell

  /Users/${USERNAME}/Applications/CoolBeans.app/Contents/Resources/app/index.js

  To ignore these parts of the path that are not predictable, you can configure AppSignal to ignore everything before the app folder as follows:

  JavaScript

  const appsignal = new AppSignal({
    matchBacktracePaths: [
      new RegExp("CoolBeans\\.app/Contents/Resources/(.*)$"),
    ],
  });

  If set, the matchBacktracePaths configuration option must contain a regular expression, or an array of one or more regular expressions, which attempt to match the whole backtrace line path. These regular expressions must have one or more match groups, such as (.*) in the example above, which attempt to match against the relevant segments of the backtrace line path.

  AppSignal will attempt to match the whole backtrace line path against these regular expressions in order. If any of the regular expression matches and produces a match group, AppSignal will replace the path in the backtrace line with the matched segment.

  Make sure your regular expressions provide unique and stable points of reference in the path, such as CoolBeans.app/Contents/Resources in the example above.

Fixed

• Fix an issue when regexes with the g global flag are used on ignoreErrors. Before this change, after successfully matching on an error to ignore, if the following error would also match the same regular expression, the regular expression would then fail to match it.

View the @appsignal/javascript v1.5.0 changelog for more information.

Changed

• Fix an issue where objects given as tags or breadcrumb metadata would have their values modified in place.

View the AppSignal JavaScript javascript v1.4.1 changelog for more information.

Changed

• Remove error throw in development mode when sending an error with send/sendError.
• The package is now useUnknownInCatchVariables compliant. Try catch blocks in the package now check for the caught variable to be an instance of Error before doing any error-specific operations with it.

View the @appsignal/javascript v1.4.0 changelog for more information.

Added

• Allow ErrorEvent instances to be reported to AppSignal.

View the @appsignal/javascript v1.3.31 changelog for more information.

Added

• Add a span override prop to the ErrorBoundary and LegacyBoundary components.

  Pass an override function to the error boundary component in order to set properties, such as tags, params or breadcrumbs, in the error span that will be sent to AppSignal.

  The override function is only called when an error is about to be sent. This allows you to only perform expensive computation to add information to the error when an error will actually be reported.

  When defined within a component, the function should be memoized with useCallback to prevent unnecessary re-renders:

  jsx

    export default const SomeComponent = ({ someProp }) => {
      const override = useCallback((span) => {
        span.setTags({ someProp })
      }, [someProp]);
   
      return (
        <ErrorBoundary override={override}>
          { /* Your component here */ }
        </ErrorBoundary>
      )
    }

View the AppSignal JavaScript react v1.0.26 changelog for more information.

Changed

• Warn about Push API key being committed in the AppSignal config file and recommend using system environment variables instead.

See the changelog for the AppSignal CLI package 1.2.8 for more information.

Report the name for Vue 3 components built using composition. It will now report the component name, rather than [unknown Vue component] as the action name for an error.

See the changelog for AppSignal for Vue package 1.1.5 for more information.

Attempt to import the http and https module dynamically. This fixes an issue with Electron, which does not expose the https module.

Emit a warning if NodeTransport is used but the https module fails to be imported.

This allows Electron users to use the AppSignal integration alongside with the electron-fetch library.

See the @appsignal/javascript 1.3.27 changelog for more information.

Support yarn workspaces when running CLI commands.

See the @appsignal/cli 1.2.6 changelog for more information.

The --config flag for the diagnose command now fails when the passed path doesn't exist.

See the @appsignal/cli 1.2.5 changelog for more information.

The --config flag allows users to specify an AppSignal configuration file to use when running the diagnose command. See the @appsignal/cli 1.2.4 changelog for more information.

Report errors when running the diagnose command. See the @appsignal/cli 1.2.3 changelog for more information.

Fix transport detection for CloudFlare module workers

Fix transport detection for CloudFlare module workers.

See the @appsignal/javascript 1.3.26 changelog for more information.

Update links to docs in installation CLI

Update links to docs in installation CLI. See the @appsignal/cli 1.2.2 changelog for more information.

Changelog update 24 August, 2022

(changelog)

• Bump peer dependency to allow React 18.2.

@appsignal/plugin-window-events@1.0.18: (changelog)

• Fix the behaviour of the unhandled promise rejection handler when the rejection event contains an Error.

@appsignal/core@1.1.18: (changelog)

• Fix isError so that it does not throw an error when the given value is not an object.

Changelog update 27 July, 2022

Fix the --[no-]send-report CLI flags for the diagnose command.

Changelog update 26 May, 2022

• Add React 18 compatibility. See our changelog for more information.