You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/platforms/javascript/guides/connect/index.mdx
+1-58
Original file line number
Diff line number
Diff line change
@@ -11,61 +11,4 @@ categories:
11
11
12
12
This guide explains how to set up Sentry in your Connect application.
13
13
14
-
Don't already have an account and Sentry project established? Head over to [sentry.io](https://sentry.io/signup/), then return to this page.
15
-
16
-
<Note>
17
-
This guide is for version 8.0.0 and up of `@sentry/node`.
18
-
</Note>
19
-
20
-
## Install
21
-
22
-
Sentry captures data by using an SDK within your application’s runtime. This means that you have to add `@sentry/node` as a runtime dependency to your application:
23
-
24
-
```bash {tabTitle:npm}
25
-
npm install --save @sentry/node
26
-
```
27
-
28
-
```bash {tabTitle:Yarn}
29
-
yarn add @sentry/node
30
-
```
31
-
32
-
## Configure
33
-
34
-
Sentry should be initialized as early in your app as possible. It is essential that you call `Sentry.init` before you require any other modules in your application—otherwise, auto-instrumentation of these modules will _not_ work.
35
-
36
-
You need to create a file named `instrument.js` that imports and initializes Sentry:
If you set a `tracesSampleRate`, performance instrumentation will automatically be enabled for you. See <PlatformLinkto="/performance/instrumentation/automatic-instrumentation">Automatic Instrumentation</PlatformLink> to learn about all the things that the SDK automatically instruments for you.
41
-
42
-
You can also manually capture performance data - see <PlatformLinkto="/performance/instrumentation/custom-instrumentation">Custom Instrumentation</PlatformLink> for details.
43
-
44
-
## Use
45
-
46
-
You need to require or import the `instrument.js` file before requiring any other modules in your application. This is necessary to ensure that Sentry can automatically instrument all modules in your application:
If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See <PlatformLinkto="/install/esm">running Sentry with ESM</PlatformLink>.
53
-
If you are unsure how you are running your application, see <PlatformLinkto="/install">Installation Methods</PlatformLink> for more information.
Learn more about manually capturing an error or message in our <PlatformLinkto="/usage/">Usage documentation</PlatformLink>.
68
-
69
-
</Note>
70
-
71
-
To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
Copy file name to clipboardExpand all lines: docs/platforms/javascript/guides/express/index.mdx
+1-58
Original file line number
Diff line number
Diff line change
@@ -11,61 +11,4 @@ categories:
11
11
12
12
This guide explains how to set up Sentry in your Express application.
13
13
14
-
Don't already have an account and Sentry project established? Head over to [sentry.io](https://sentry.io/signup/), then return to this page.
15
-
16
-
<Note>This guide is for version 8.0.0 and up of `@sentry/node`.</Note>
17
-
18
-
## Install
19
-
20
-
Sentry captures data by using an SDK within your application’s runtime. This means that you have to add `@sentry/node` as a runtime dependency to your application:
21
-
22
-
```bash {tabTitle:npm}
23
-
npm install --save @sentry/node
24
-
```
25
-
26
-
```bash {tabTitle:Yarn}
27
-
yarn add @sentry/node
28
-
```
29
-
30
-
## Configure
31
-
32
-
Sentry should be initialized as early in your app as possible. It is essential that you call `Sentry.init` before you require any other modules in your application—otherwise, auto-instrumentation of these modules will _not_ work.
33
-
34
-
Once this is done, Sentry's Node SDK captures unhandled exceptions as well as tracing data for your application.
35
-
36
-
You need to create a file named `instrument.js` that imports and initializes Sentry:
If you set a `tracesSampleRate`, performance instrumentation will automatically be enabled for you. See <PlatformLinkto="/performance/instrumentation/automatic-instrumentation">Automatic Instrumentation</PlatformLink> to learn about all the things that the SDK automatically instruments for you.
41
-
42
-
You can also manually capture performance data - see <PlatformLinkto="/performance/instrumentation/custom-instrumentation">Custom Instrumentation</PlatformLink> for details.
43
-
44
-
## Use
45
-
46
-
You need to require or import the `instrument.js` file before requiring any other modules in your application. This is necessary to ensure that Sentry can automatically instrument all modules in your application:
If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See <PlatformLinkto="/install/esm">running Sentry with ESM</PlatformLink>.
53
-
If you are unsure how you are running your application, see <PlatformLinkto="/install">Installation Methods</PlatformLink> for more information.
Learn more about manually capturing an error or message in our <PlatformLinkto="/usage/">Usage documentation</PlatformLink>.
68
-
69
-
</Note>
70
-
71
-
To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
Copy file name to clipboardExpand all lines: docs/platforms/javascript/guides/fastify/index.mdx
+1-58
Original file line number
Diff line number
Diff line change
@@ -11,61 +11,4 @@ categories:
11
11
12
12
This guide explains how to set up Sentry in your Fastify application.
13
13
14
-
Don't already have an account and Sentry project established? Head over to [sentry.io](https://sentry.io/signup/), then return to this page.
15
-
16
-
<Note>This guide is for version 8.0.0 and up of `@sentry/node`.</Note>
17
-
18
-
## Install
19
-
20
-
Sentry captures data by using an SDK within your application’s runtime. This means that you have to add `@sentry/node` as a runtime dependency to your application:
21
-
22
-
```bash {tabTitle:npm}
23
-
npm install --save @sentry/node
24
-
```
25
-
26
-
```bash {tabTitle:Yarn}
27
-
yarn add @sentry/node
28
-
```
29
-
30
-
## Configure
31
-
32
-
Sentry should be initialized as early in your app as possible. It is essential that you call `Sentry.init` before you require any other modules in your application—otherwise, auto-instrumentation of these modules will _not_ work.
33
-
34
-
Once this is done, Sentry's Node SDK captures unhandled exceptions as well as tracing data for your application.
35
-
36
-
You need to create a file named `instrument.js` that imports and initializes Sentry:
If you set a `tracesSampleRate`, performance instrumentation will automatically be enabled for you. See <PlatformLinkto="/performance/instrumentation/automatic-instrumentation">Automatic Instrumentation</PlatformLink> to learn about all the things that the SDK automatically instruments for you.
41
-
42
-
You can also manually capture performance data - see <PlatformLinkto="/performance/instrumentation/custom-instrumentation">Custom Instrumentation</PlatformLink> for details.
43
-
44
-
## Use
45
-
46
-
You need to require or import the `instrument.js` file before requiring any other modules in your application. This is necessary to ensure that Sentry can automatically instrument all modules in your application:
If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See <PlatformLinkto="/install/esm">running Sentry with ESM</PlatformLink>.
53
-
If you are unsure how you are running your application, see <PlatformLinkto="/install">Installation Methods</PlatformLink> for more information.
Learn more about manually capturing an error or message in our <PlatformLinkto="/usage/">Usage documentation</PlatformLink>.
68
-
69
-
</Note>
70
-
71
-
To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
Copy file name to clipboardExpand all lines: docs/platforms/javascript/guides/hapi/index.mdx
+1-60
Original file line number
Diff line number
Diff line change
@@ -11,63 +11,4 @@ categories:
11
11
12
12
This guide explains how to set up Sentry in your Hapi application.
13
13
14
-
Don't already have an account and Sentry project established? Head over to [sentry.io](https://sentry.io/signup/), then return to this page.
15
-
16
-
<Note>
17
-
This guide is for version 8.0.0 and up of `@sentry/node`.
18
-
</Note>
19
-
20
-
## Install
21
-
22
-
Sentry captures data by using an SDK within your application’s runtime. This means that you have to add `@sentry/node` as a runtime dependency to your application:
23
-
24
-
```bash {tabTitle:npm}
25
-
npm install --save @sentry/node
26
-
```
27
-
28
-
```bash {tabTitle:Yarn}
29
-
yarn add @sentry/node
30
-
```
31
-
32
-
## Configure
33
-
34
-
Sentry should be initialized as early in your app as possible. It is essential that you call `Sentry.init` before you require any other modules in your application—otherwise, auto-instrumentation of these modules will _not_ work.
35
-
36
-
Once this is done, Sentry's Node SDK captures unhandled exceptions as well as tracing data for your application.
37
-
38
-
You need to create a file named `instrument.js` that imports and initializes Sentry:
If you set a `tracesSampleRate`, performance instrumentation will automatically be enabled for you. See <PlatformLinkto="/performance/instrumentation/automatic-instrumentation">Automatic Instrumentation</PlatformLink> to learn about all the things that the SDK automatically instruments for you.
43
-
44
-
You can also manually capture performance data - see <PlatformLinkto="/performance/instrumentation/custom-instrumentation">Custom Instrumentation</PlatformLink> for details.
45
-
46
-
## Use
47
-
48
-
You need to require or import the `instrument.js` file before requiring any other modules in your application. This is necessary to ensure that Sentry can automatically instrument all modules in your application:
If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See <PlatformLinkto="/install/esm">running Sentry with ESM</PlatformLink>.
55
-
If you are unsure how you are running your application, see <PlatformLinkto="/install">Installation Methods</PlatformLink> for more information.
Learn more about manually capturing an error or message in our <PlatformLinkto="/usage/">Usage documentation</PlatformLink>.
70
-
71
-
</Note>
72
-
73
-
To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
Copy file name to clipboardExpand all lines: docs/platforms/javascript/guides/koa/index.mdx
+1-60
Original file line number
Diff line number
Diff line change
@@ -11,63 +11,4 @@ categories:
11
11
12
12
This guide explains how to set up Sentry in your Koa application.
13
13
14
-
Don't already have an account and Sentry project established? Head over to [sentry.io](https://sentry.io/signup/), then return to this page.
15
-
16
-
<Note>
17
-
This guide is for version 8.0.0 and up of `@sentry/node`.
18
-
</Note>
19
-
20
-
## Install
21
-
22
-
Sentry captures data by using an SDK within your application’s runtime. This means that you have to add `@sentry/node` as a runtime dependency to your application:
23
-
24
-
```bash {tabTitle:npm}
25
-
npm install --save @sentry/node
26
-
```
27
-
28
-
```bash {tabTitle:Yarn}
29
-
yarn add @sentry/node
30
-
```
31
-
32
-
## Configure
33
-
34
-
Sentry should be initialized as early in your app as possible. It is essential that you call `Sentry.init` before you require any other modules in your application—otherwise, auto-instrumentation of these modules will _not_ work.
35
-
36
-
Once this is done, Sentry's Node SDK captures unhandled exceptions as well as tracing data for your application.
37
-
38
-
You need to create a file named `instrument.js` that imports and initializes Sentry:
If you set a `tracesSampleRate`, performance instrumentation will automatically be enabled for you. See <PlatformLinkto="/performance/instrumentation/automatic-instrumentation">Automatic Instrumentation</PlatformLink> to learn about all the things that the SDK automatically instruments for you.
43
-
44
-
You can also manually capture performance data - see <PlatformLinkto="/performance/instrumentation/custom-instrumentation">Custom Instrumentation</PlatformLink> for details.
45
-
46
-
## Use
47
-
48
-
You need to require or import the `instrument.js` file before requiring any other modules in your application. This is necessary to ensure that Sentry can automatically instrument all modules in your application:
If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See <PlatformLinkto="/install/esm">running Sentry with ESM</PlatformLink>.
55
-
If you are unsure how you are running your application, see <PlatformLinkto="/install">Installation Methods</PlatformLink> for more information.
Learn more about manually capturing an error or message in our <PlatformLinkto="/usage/">Usage documentation</PlatformLink>.
70
-
71
-
</Note>
72
-
73
-
To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
Copy file name to clipboardExpand all lines: docs/platforms/javascript/guides/nestjs/index.mdx
+1-53
Original file line number
Diff line number
Diff line change
@@ -11,56 +11,4 @@ categories:
11
11
12
12
This guide explains how to set up Sentry in your Nest.js application.
13
13
14
-
Don't already have an account and Sentry project established? Head over to [sentry.io](https://sentry.io/signup/), then return to this page.
15
-
16
-
<Note>
17
-
This guide is for version 8.0.0 and up of `@sentry/node`.
18
-
</Note>
19
-
20
-
## Install
21
-
22
-
Sentry captures data by using an SDK within your application’s runtime. This means that you have to add `@sentry/node` as a runtime dependency to your application:
23
-
24
-
```bash {tabTitle:npm}
25
-
npm install --save @sentry/node
26
-
```
27
-
28
-
```bash {tabTitle:Yarn}
29
-
yarn add @sentry/node
30
-
```
31
-
32
-
## Configure
33
-
34
-
Sentry should be initialized as early in your app as possible. It is essential that you call `Sentry.init` before you require any other modules in your application—otherwise, auto-instrumentation of these modules will _not_ work.
35
-
36
-
Once this is done, Sentry's Node SDK captures unhandled exceptions as well as tracing data for your application.
37
-
38
-
You need to create a file named `instrument.js` that imports and initializes Sentry:
If you set a `tracesSampleRate`, performance instrumentation will automatically be enabled for you. See <PlatformLinkto="/performance/instrumentation/automatic-instrumentation">Automatic Instrumentation</PlatformLink> to learn about all the things that the SDK automatically instruments for you.
43
-
44
-
You can also manually capture performance data - see <PlatformLinkto="/performance/instrumentation/custom-instrumentation">Custom Instrumentation</PlatformLink> for details.
45
-
46
-
## Use
47
-
48
-
You need to require or import the `instrument.js` file before requiring any other modules in your application. This is necessary to ensure that Sentry can automatically instrument all modules in your application:
Learn more about manually capturing an error or message in our <PlatformLinkto="/usage/">Usage documentation</PlatformLink>.
63
-
64
-
</Note>
65
-
66
-
To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
0 commit comments