diff --git a/develop-docs/sdk/expected-features/setup-wizards/index.mdx b/develop-docs/sdk/expected-features/setup-wizards/index.mdx index 138dea175ec597..e03d81fbf0e8e5 100644 --- a/develop-docs/sdk/expected-features/setup-wizards/index.mdx +++ b/develop-docs/sdk/expected-features/setup-wizards/index.mdx @@ -142,7 +142,7 @@ If you create a new prompt, make sure you wrap it with the [`abortIfCancelled`]( This will take care of correctly handling Cmd+C inputs, flushing Sentry events (if using [telemetry](#telemetry)) and exiting the process. For example: -```TypeScript +```typescript const continueWithoutGit = await abortIfCancelled( clack.confirm({ message: @@ -236,7 +236,7 @@ This helps us understand how our users use the wizard, which actions they take a It's easiest to use the `withTelemetery` wrapper function that's available in the `@sentry/wizard` package: -```TypeScript +```typescript export async function runSourcemapsWizard( options: WizardOptions, ): Promise { @@ -254,7 +254,7 @@ This will create a minimal Sentry client and send events, such as sessions, tran If you want to add spans to individual steps within a wizard flow, you can use the `traceStep` helper function: -```TypeScript +```typescript const res = await traceStep('npm-script-setup', () => setupNpmScriptInCI()); ``` diff --git a/develop-docs/sdk/platform-specifics/serverless-sdks/aws-lambda.mdx b/develop-docs/sdk/platform-specifics/serverless-sdks/aws-lambda.mdx index 8ddb7a925a6f4b..2a0fd1d074031f 100644 --- a/develop-docs/sdk/platform-specifics/serverless-sdks/aws-lambda.mdx +++ b/develop-docs/sdk/platform-specifics/serverless-sdks/aws-lambda.mdx @@ -3,9 +3,9 @@ title: AWS Lambda sidebar_order: 10 --- -Lambda functions can be written in numerous programming languages (Javascript, +Lambda functions can be written in numerous programming languages (JavaScript, Python, Ruby, Java, Go, ...). Sentry is currently supporting automatic -instrumentation of Lambda functions written in Javascript and Python. +instrumentation of Lambda functions written in JavaScript and Python. See the [Sentry Documentation](https://docs.sentry.io/product/integrations/cloud-monitoring/) on how to set up serverless instrumentation. @@ -29,7 +29,7 @@ like the Sentry SDK to your Lambda function. With the AWS Lambda Integrations users can add Sentry functionality to their Lambda function without changing the code of the Lambda function. -Sentry is providing a Lambda Layer including the Javascript SDK (or Python +Sentry is providing a Lambda Layer including the JavaScript SDK (or Python SDK). See the documentation to learn how customers can instrument their Lambda @@ -42,7 +42,7 @@ Sentry is deploying one Lambda Layer for Node-based Lambda functions functions (`SentryPythonServerlessSDK`). Those Lambda layers are distributed to various AWS regions to be close to the users. -Both these layers include the latest Sentry Javascript SDK (or Python SDK). +Both these layers include the latest Sentry JavaScript SDK (or Python SDK). ### Building of the Python Layer @@ -62,20 +62,20 @@ this can be found [here](https://github.com/getsentry/sentry-python/blob/master/ To deploy a new version of the Lambda layer to AWS, you need to trigger a new release of the Python SDK. -### Building of the Javascript/Node Layer +### Building of the JavaScript/Node Layer -The contents of the Layer directory for the Javascript/Node layer are built during the +The contents of the Layer directory for the JavaScript/Node layer are built during the "Build & Test" workflow in Github actions. The steps necessary can be found [here](https://github.com/getsentry/sentry-javascript/blob/master/.github/workflows/build.yml). This will prepare the Lambda layer directory, compress everything and upload the resulting zip file as an artifact to GitHub. -### Deployment of the Javascript/Node Layer +### Deployment of the JavaScript/Node Layer The zip file prepared in the previous step will be deployed to AWS Lambda by [Craft](https://github.com/getsentry/craft). The configuration of craft for doing this can be found [here](https://github.com/getsentry/sentry-javascript/blob/master/.craft.yml). To deploy a new version of the Lambda layer to AWS, you need to trigger a new -release of the Javascript SDK. +release of the JavaScript SDK. diff --git a/develop-docs/sdk/telemetry/traces/tracing-without-performance.mdx b/develop-docs/sdk/telemetry/traces/tracing-without-performance.mdx index 1cfa8ef4e1d0bf..000359aa576429 100644 --- a/develop-docs/sdk/telemetry/traces/tracing-without-performance.mdx +++ b/develop-docs/sdk/telemetry/traces/tracing-without-performance.mdx @@ -22,7 +22,7 @@ This means that SDKs by default always: TwP is active by default if users don't specify sampling options that enable span collection and sending (i.e. [regular tracing](#enable-regular-tracing)). For example, the following trivial SDK setup (note the absence of sampling options) enables TwP: -```JavaScript +```javascript Sentry.init({ dsn: "___PUBLIC_DSN___", }); diff --git a/docs/platforms/javascript/common/configuration/filtering.mdx b/docs/platforms/javascript/common/configuration/filtering.mdx index 684006a14723ad..b6f1d523fb8386 100644 --- a/docs/platforms/javascript/common/configuration/filtering.mdx +++ b/docs/platforms/javascript/common/configuration/filtering.mdx @@ -227,7 +227,7 @@ Learn more about configuring the sam ## Filtering Spans -Available since Javascript SDK version `8.2.0`. +Available since JavaScript SDK version `8.2.0`. To prevent certain spans from being reported to Sentry, use the configuration option which allows you to provide a function to modify and drop a child span. This function is only called for child spans of the root span. If you want to modify or drop the root span, including its child spans, use [`beforeSendTransaction`](#using-beforesendtransaction) instead. diff --git a/docs/platforms/javascript/common/configuration/integrations/inboundfilters.mdx b/docs/platforms/javascript/common/configuration/integrations/inboundfilters.mdx index 95e4e608607a47..efabcf626d75cd 100644 --- a/docs/platforms/javascript/common/configuration/integrations/inboundfilters.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/inboundfilters.mdx @@ -9,11 +9,11 @@ This integration is enabled by default. If you'd like to modify your default int This integration allows you to ignore specific errors based on the type, message, or URLs in a given exception. -By default, it'll ignore errors that start with `Script error` or `Javascript error: Script error`. +By default, it'll ignore errors that start with `Script error` or `JavaScript error: Script error`. To configure this integration, use the `ignoreErrors`, `ignoreTransactions`, `denyUrls`, and `allowUrls` SDK options directly. For example: -```JavaScript +```javascript Sentry.init({ ignoreErrors: ["ignore-this-error"], }); diff --git a/docs/platforms/javascript/common/profiling/browser-profiling.mdx b/docs/platforms/javascript/common/profiling/browser-profiling.mdx index 134e4890581fea..a8cd67a6287c6a 100644 --- a/docs/platforms/javascript/common/profiling/browser-profiling.mdx +++ b/docs/platforms/javascript/common/profiling/browser-profiling.mdx @@ -80,4 +80,4 @@ What does Sentry's JavaScript browser profile offer that Chrome DevTools does no Please note, that since the browser profiling API is currently only implemented in Chromium-based browsers, the profiles collected with Sentry's JavaScript browser profiling will inherently be biased toward that demographic. This is something that you'll need to consider if you're basing your decisions on the data collected. -We hope that as the Javascript browser profiling API gains adoption, other browsers will implement it as well. If you find the browser profiling feature helpful and would like to see it gain further adoption, please consider supporting the spec at the official WICG repository. +We hope that as the JavaScript browser profiling API gains adoption, other browsers will implement it as well. If you find the browser profiling feature helpful and would like to see it gain further adoption, please consider supporting the spec at the official WICG repository. diff --git a/docs/platforms/react-native/integrations/default.mdx b/docs/platforms/react-native/integrations/default.mdx index b960c8fdb23436..60200879aaf895 100644 --- a/docs/platforms/react-native/integrations/default.mdx +++ b/docs/platforms/react-native/integrations/default.mdx @@ -14,7 +14,7 @@ _Import name: `Sentry.inboundFiltersIntegration`_ This integration allows you to ignore specific errors based on the type, message, or URLs in a given exception. -By default, it'll ignore errors that start with `Script error` or `Javascript error: Script error`. +By default, it'll ignore errors that start with `Script error` or `JavaScript error: Script error`. To configure this integration, use the `ignoreErrors`, `ignoreTransactions`, `denyUrls`, and `allowUrls` SDK options directly. Keep in mind that `denyURLs` and `allowURLs` diff --git a/docs/platforms/react-native/manual-setup/native-init.mdx b/docs/platforms/react-native/manual-setup/native-init.mdx index 62055b5dd1bbfd..b35d65e786ee86 100644 --- a/docs/platforms/react-native/manual-setup/native-init.mdx +++ b/docs/platforms/react-native/manual-setup/native-init.mdx @@ -35,7 +35,7 @@ you have to [configure the sample rate](/platforms/apple/tracing/#configure-the- -Initializing with this method uses a Content Provider. Because the Javascript engine for React Native is also initialized using a Content Provider, we cannot guarantee that Sentry will always initialize before the JavaScript engine. +Initializing with this method uses a Content Provider. Because the JavaScript engine for React Native is also initialized using a Content Provider, we cannot guarantee that Sentry will always initialize before the JavaScript engine. diff --git a/docs/platforms/react-native/migration/before-v5.mdx b/docs/platforms/react-native/migration/before-v5.mdx index ac49a5f3396505..8c64e41ae5f3ea 100644 --- a/docs/platforms/react-native/migration/before-v5.mdx +++ b/docs/platforms/react-native/migration/before-v5.mdx @@ -100,7 +100,7 @@ See the JS SDK migration guide [here](https://github.com/getsentry/sentry-javasc ## From 3.x to 4.x -By bumping Sentry JavaScript to v7, new breaking changes were introduced, to learn more about what was changed, check out the [breaking changes changelog](https://github.com/getsentry/sentry-javascript/blob/7.0.0/CHANGELOG.md#breaking-changes) from Sentry Javascript. +By bumping Sentry JavaScript to v7, new breaking changes were introduced, to learn more about what was changed, check out the [breaking changes changelog](https://github.com/getsentry/sentry-javascript/blob/7.0.0/CHANGELOG.md#breaking-changes) from Sentry JavaScript. By bumping Sentry Android to v6, new breaking changes were introduced, to learn more about what was changed, check out the [migration guide](/platforms/android/migration/#migrating-from-iosentrysentry-android-5x-to-iosentrysentry-android-600). diff --git a/docs/platforms/react-native/sourcemaps/uploading/expo-advanced.mdx b/docs/platforms/react-native/sourcemaps/uploading/expo-advanced.mdx index 3ede027e327844..ff1bbdff3a7537 100644 --- a/docs/platforms/react-native/sourcemaps/uploading/expo-advanced.mdx +++ b/docs/platforms/react-native/sourcemaps/uploading/expo-advanced.mdx @@ -154,7 +154,7 @@ npx sentry-cli sourcemaps upload \ ## Manual Upload for JSC Release -After the Sentry Expo Plugin and Sentry Metro plugin are added to the application configuration, generate and upload Javascript Core source maps. +After the Sentry Expo Plugin and Sentry Metro plugin are added to the application configuration, generate and upload JavaScript Core source maps. ### Generate Bundle diff --git a/docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx index fd04bec5414ae4..bb48ac848a92a5 100644 --- a/docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx @@ -93,7 +93,7 @@ We track stalls that occur in your React Native app during a transaction and pro ### Fetch/XML Request Instrumentation -The tracing integration creates a child span for every `XMLHttpRequest` or `fetch` request on the Javascript layer that occurs while those transactions are open. Learn more about [traces, transactions, and spans](/product/sentry-basics/tracing/distributed-tracing/). +The tracing integration creates a child span for every `XMLHttpRequest` or `fetch` request on the JavaScript layer that occurs while those transactions are open. Learn more about [traces, transactions, and spans](/product/sentry-basics/tracing/distributed-tracing/). ## Configuration Options diff --git a/docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx b/docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx index 0527896e6768c7..8b1c3610adfc10 100644 --- a/docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx +++ b/docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx @@ -24,7 +24,7 @@ Google considers Core Web Vitals to be the most important metrics for measuring ### Interaction to Next Paint (INP) -On March 12, 2024, Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital. Prior to this, INP was an experimental metric that Sentry did not collect. To begin collecting INP measurements, make sure your Javascript SDK version is [7.104.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.104.0) or higher and that the option [`enableInp`](/platforms/javascript/tracing/instrumentation/automatic-instrumentation/#enableinp) is on. +On March 12, 2024, Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital. Prior to this, INP was an experimental metric that Sentry did not collect. To begin collecting INP measurements, make sure your JavaScript SDK version is [7.104.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.104.0) or higher and that the option [`enableInp`](/platforms/javascript/tracing/instrumentation/automatic-instrumentation/#enableinp) is on. [Interaction to Next Paint (INP)](https://web.dev/articles/inp) measures the time from when a user interacts with a page (through a click, tap, or keyboard input) to when the next paint (rendering of content on the screen) occurs. INP aims to assess how quickly users see a response from the website after taking an action, which is crucial for providing a smooth and responsive user experience. diff --git a/includes/debug-id-requirement.mdx b/includes/debug-id-requirement.mdx index d86bb6a6049a63..51a460e2a3f041 100644 --- a/includes/debug-id-requirement.mdx +++ b/includes/debug-id-requirement.mdx @@ -3,6 +3,6 @@ This guide assumes the following: - `sentry-cli` version >= `2.17.0` -- Sentry Javascript SDK version >= `7.47.0` +- Sentry JavaScript SDK version >= `7.47.0` diff --git a/platform-includes/getting-started-config/javascript.react.mdx b/platform-includes/getting-started-config/javascript.react.mdx index 33ab0f746408ce..bee80881ea6c85 100644 --- a/platform-includes/getting-started-config/javascript.react.mdx +++ b/platform-includes/getting-started-config/javascript.react.mdx @@ -84,7 +84,7 @@ These hooks apply to all React components that are mounted to the container whic ### Add Error Boundary -If you're using React 16 or above, you can use the [Error Boundary](features/error-boundary/) component to automatically send Javascript errors from inside a component tree to Sentry, and set a fallback UI. +If you're using React 16 or above, you can use the [Error Boundary](features/error-boundary/) component to automatically send JavaScript errors from inside a component tree to Sentry, and set a fallback UI. ### Set Up React Router diff --git a/platform-includes/getting-started-install/javascript.mdx b/platform-includes/getting-started-install/javascript.mdx index 28f8993139551c..75dfbc2276f86c 100644 --- a/platform-includes/getting-started-install/javascript.mdx +++ b/platform-includes/getting-started-install/javascript.mdx @@ -32,4 +32,4 @@ We also support installation via [CDN bundles](/platforms/javascript/install/loa If you're updating your Sentry SDK to the latest version, check out our [migration guide](https://github.com/getsentry/sentry-javascript/blob/master/MIGRATION.md) to learn more about breaking changes. -If you are using our previous Browser Javascript SDK, you can access the legacy SDK documentation, until further notice. +If you are using our previous Browser JavaScript SDK, you can access the legacy SDK documentation, until further notice. diff --git a/platform-includes/performance/connect-services/javascript.mdx b/platform-includes/performance/connect-services/javascript.mdx index 8402565f2f0f7a..ddd73749b256e5 100644 --- a/platform-includes/performance/connect-services/javascript.mdx +++ b/platform-includes/performance/connect-services/javascript.mdx @@ -4,7 +4,7 @@ For traces that begin in the front end, any requests made (and any requests your -The `baggage` header was added with version 7 of the Sentry Javascript SDK and is not yet standardized across other Sentry SDKs. It is part of an ongoing effort to create a more frictionless and targeted sampling approach, and its content is subject to change. +The `baggage` header was added with version 7 of the Sentry JavaScript SDK and is not yet standardized across other Sentry SDKs. It is part of an ongoing effort to create a more frictionless and targeted sampling approach, and its content is subject to change.