feat(js/deno): Remove options xhr, history and dom from deno breadcrumbs

[s1gr1d]

Description of changes

In this PR getsentry/sentry-javascript#10867, the options xhr, history and dom were removed from the breadcrumbs Integration for Deno. The base for the breadcrumbs docs file is located in commons.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sentry-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 5, 2024 1:18pm

[codecov]

Bundle Report

Changes will increase total bundle size by 279 bytes ⬆️

Bundle name	Size	Change
sentry-docs-server	5.93MB	285 bytes ⬆️
sentry-docs-edge-server	3.47kB	0 bytes
sentry-docs-client	5.51MB	6 bytes ⬇️

[stephanie-anderson]

If you create a page in a guide, you do not longer need to specify for with other platforms/guides is isn't supported. You could remove the notSupported list

[lizokm]

Thanks for writing this doc @s1gr1d and welcome to Sentry!! This looks great overall, I just have a few small suggestions :)

[lizokm]

Suggested change

	description: "Wraps native APIs to capture breadcrumbs. (default)"
	description: "Learn how the JavaScript framework Deno wraps native APIs to capture breadcrumbs."

[lizokm]

Suggested change

	This integration is [enabled by default](./../#modifying-default-integrations).
	This integration wraps native APIs to capture breadcrumbs. By default, the Sentry SDK wraps all APIs.
	You can opt-out of capturing breadcrumbs for specific parts of your application (e.g. do not capture `console.log` calls as breadcrumbs) via the options below.
	In
	When you're using Sentry's SDK for Deno, the breadcrumbs-capture integration wraps native APIs to capture breadcrumbs. Because the Sentry SDK wraps all APIs, this integration is enabled by default. Read about how to modify default integrations [here](./../#modifying-default-integrations).
	You can opt out of capturing breadcrumbs for specific parts of your application (for example, you could say don't capture `console.log` calls as breadcrumbs) via the options below.

We try to stay away from Latin abbreviations (eg, etc,...)
We also use contractions as much as possible (do not > don't)
:)

[s1gr1d]

I actually find it useful to have the information that this is a default integration at the top :) I also talked to @lforst and he also thinks that having that really short at the top is better.

What do you think of that:

This integration is enabled by default. You can also modify default integrations.

The breadcrumbsIntegration wraps native APIs to capture breadcrumbs. By default, the Sentry SDK wraps all APIs. You can opt out of capturing breadcrumbs for specific parts of your application (for example, you could say don't capture console.log calls as breadcrumbs) via the options below.

As all other pages with default integrations have this first line "This integration is enabled by default", I would modify the "base page" for integrations too in another PR - #9308 :)

[lizokm]

Suggested change

	### `console`
	_Type: `boolean`_
	Log calls to `console.log`, `console.debug`, etc.
	### `fetch`
	_Type: `boolean`_
	Log HTTP requests done with the Fetch API
	### `sentry`
	_Type: `boolean`_
	Log whenever we send an event to the server.
	`console`
	_Type: `boolean`_
	Log calls to `console.log`, `console.debug`, and so on.
	`fetch`
	_Type: `boolean`_
	Log HTTP requests done with the Fetch API.
	`sentry`
	_Type: `boolean`_
	Log whenever we send an event to the server.

[s1gr1d]

I think we still need this, as people can directly link to the H3 of the option.

[lizokm]

Looks good, just one more small tweak :)

[lizokm]

Suggested change

	This integration is enabled by default. You can also [modify default integrations](./../#modifying-default-integrations).
	This integration is enabled by default. If you'd like to modify your default integrations, read [this](./../#modifying-default-integrations).

[lizokm]

Suggested change

	Log HTTP requests done with the Fetch API
	Log HTTP requests done with the Fetch API.