@wildo-ai/external-connectors-public 1.1.2 → 1.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/esm/.native.tsbuildinfo +1 -0
- package/dist/esm/app/compose-frontend-app-providers.d.ts.map +1 -1
- package/dist/esm/app/compose-frontend-app-providers.js +5 -2
- package/dist/esm/app/compose-frontend-app-providers.js.map +1 -1
- package/dist/esm/app/compose-hydrated-frontend-app-providers.d.ts +33 -0
- package/dist/esm/app/compose-hydrated-frontend-app-providers.d.ts.map +1 -0
- package/dist/esm/app/compose-hydrated-frontend-app-providers.js +41 -0
- package/dist/esm/app/compose-hydrated-frontend-app-providers.js.map +1 -0
- package/dist/esm/app/engine-frontend-app-provider-registry.d.ts.map +1 -1
- package/dist/esm/app/engine-frontend-app-provider-registry.js +4 -0
- package/dist/esm/app/engine-frontend-app-provider-registry.js.map +1 -1
- package/dist/esm/app/frontend-app-provider-module.types.d.ts +128 -15
- package/dist/esm/app/frontend-app-provider-module.types.d.ts.map +1 -1
- package/dist/esm/app/frontend-app-provider-module.types.js +7 -6
- package/dist/esm/app/frontend-app-provider-module.types.js.map +1 -1
- package/dist/esm/app/index.d.ts +4 -0
- package/dist/esm/app/index.d.ts.map +1 -1
- package/dist/esm/app/index.js +4 -0
- package/dist/esm/app/index.js.map +1 -1
- package/dist/esm/companion-exports.d.ts +47 -0
- package/dist/esm/companion-exports.d.ts.map +1 -1
- package/dist/esm/companion-exports.js +99 -5
- package/dist/esm/companion-exports.js.map +1 -1
- package/dist/esm/engine-frontend-providers-package.d.ts +7 -0
- package/dist/esm/engine-frontend-providers-package.d.ts.map +1 -0
- package/dist/esm/engine-frontend-providers-package.js +7 -0
- package/dist/esm/engine-frontend-providers-package.js.map +1 -0
- package/dist/esm/providers/algolia/algolia.frontend-techdoc.module.d.ts.map +1 -1
- package/dist/esm/providers/algolia/algolia.frontend-techdoc.module.js +26 -4
- package/dist/esm/providers/algolia/algolia.frontend-techdoc.module.js.map +1 -1
- package/dist/esm/providers/apple/apple.frontend-app.module.d.ts.map +1 -1
- package/dist/esm/providers/apple/apple.frontend-app.module.js +16 -4
- package/dist/esm/providers/apple/apple.frontend-app.module.js.map +1 -1
- package/dist/esm/providers/github/github.frontend-app.module.d.ts.map +1 -1
- package/dist/esm/providers/github/github.frontend-app.module.js +15 -4
- package/dist/esm/providers/github/github.frontend-app.module.js.map +1 -1
- package/dist/esm/providers/google/google.frontend-app.module.d.ts.map +1 -1
- package/dist/esm/providers/google/google.frontend-app.module.js +16 -4
- package/dist/esm/providers/google/google.frontend-app.module.js.map +1 -1
- package/dist/esm/providers/microsoft/microsoft.frontend-app.module.d.ts.map +1 -1
- package/dist/esm/providers/microsoft/microsoft.frontend-app.module.js +15 -4
- package/dist/esm/providers/microsoft/microsoft.frontend-app.module.js.map +1 -1
- package/dist/esm/providers/posthog/posthog.frontend-website.module.d.ts +19 -0
- package/dist/esm/providers/posthog/posthog.frontend-website.module.d.ts.map +1 -1
- package/dist/esm/providers/posthog/posthog.frontend-website.module.js +65 -4
- package/dist/esm/providers/posthog/posthog.frontend-website.module.js.map +1 -1
- package/dist/esm/providers/recaptcha/recaptcha.frontend-website.module.d.ts.map +1 -1
- package/dist/esm/providers/recaptcha/recaptcha.frontend-website.module.js +24 -4
- package/dist/esm/providers/recaptcha/recaptcha.frontend-website.module.js.map +1 -1
- package/dist/esm/providers/sentry/index.d.ts +0 -2
- package/dist/esm/providers/sentry/index.d.ts.map +0 -1
- package/dist/esm/providers/sentry/index.js +0 -2
- package/dist/esm/providers/sentry/index.js.map +0 -1
- package/dist/esm/providers/sentry/sentry.frontend-app.module.d.ts +57 -0
- package/dist/esm/providers/sentry/sentry.frontend-app.module.d.ts.map +1 -0
- package/dist/esm/providers/sentry/sentry.frontend-app.module.js +141 -0
- package/dist/esm/providers/sentry/sentry.frontend-app.module.js.map +1 -0
- package/dist/esm/providers/sentry/sentry.frontend-website.module.d.ts +27 -0
- package/dist/esm/providers/sentry/sentry.frontend-website.module.d.ts.map +1 -1
- package/dist/esm/providers/sentry/sentry.frontend-website.module.js +79 -4
- package/dist/esm/providers/sentry/sentry.frontend-website.module.js.map +1 -1
- package/dist/esm/providers/stripe/stripe.frontend-app.module.d.ts.map +1 -1
- package/dist/esm/providers/stripe/stripe.frontend-app.module.js +15 -4
- package/dist/esm/providers/stripe/stripe.frontend-app.module.js.map +1 -1
- package/dist/esm/shared/activate-frontend-provider-sdks.d.ts +88 -0
- package/dist/esm/shared/activate-frontend-provider-sdks.d.ts.map +1 -0
- package/dist/esm/shared/activate-frontend-provider-sdks.js +110 -0
- package/dist/esm/shared/activate-frontend-provider-sdks.js.map +1 -0
- package/dist/esm/shared/frontend-provider-surface.types.d.ts +365 -0
- package/dist/esm/shared/frontend-provider-surface.types.d.ts.map +1 -0
- package/dist/esm/shared/frontend-provider-surface.types.js +82 -0
- package/dist/esm/shared/frontend-provider-surface.types.js.map +1 -0
- package/dist/esm/shared/hydrate-frontend-providers.d.ts +150 -0
- package/dist/esm/shared/hydrate-frontend-providers.d.ts.map +1 -0
- package/dist/esm/shared/hydrate-frontend-providers.js +298 -0
- package/dist/esm/shared/hydrate-frontend-providers.js.map +1 -0
- package/dist/esm/techdoc/compose-frontend-techdoc-providers.d.ts.map +1 -1
- package/dist/esm/techdoc/compose-frontend-techdoc-providers.js +5 -2
- package/dist/esm/techdoc/compose-frontend-techdoc-providers.js.map +1 -1
- package/dist/esm/techdoc/compose-hydrated-frontend-techdoc-providers.d.ts +33 -0
- package/dist/esm/techdoc/compose-hydrated-frontend-techdoc-providers.d.ts.map +1 -0
- package/dist/esm/techdoc/compose-hydrated-frontend-techdoc-providers.js +41 -0
- package/dist/esm/techdoc/compose-hydrated-frontend-techdoc-providers.js.map +1 -0
- package/dist/esm/techdoc/frontend-techdoc-provider-module.types.d.ts +61 -4
- package/dist/esm/techdoc/frontend-techdoc-provider-module.types.d.ts.map +1 -1
- package/dist/esm/techdoc/frontend-techdoc-provider-module.types.js +5 -3
- package/dist/esm/techdoc/frontend-techdoc-provider-module.types.js.map +1 -1
- package/dist/esm/techdoc/index.d.ts +4 -0
- package/dist/esm/techdoc/index.d.ts.map +1 -1
- package/dist/esm/techdoc/index.js +4 -0
- package/dist/esm/techdoc/index.js.map +1 -1
- package/dist/esm/website/compose-frontend-website-providers.d.ts.map +1 -1
- package/dist/esm/website/compose-frontend-website-providers.js +5 -2
- package/dist/esm/website/compose-frontend-website-providers.js.map +1 -1
- package/dist/esm/website/compose-hydrated-frontend-website-providers.d.ts +33 -0
- package/dist/esm/website/compose-hydrated-frontend-website-providers.d.ts.map +1 -0
- package/dist/esm/website/compose-hydrated-frontend-website-providers.js +41 -0
- package/dist/esm/website/compose-hydrated-frontend-website-providers.js.map +1 -0
- package/dist/esm/website/engine-frontend-website-provider-registry.d.ts.map +1 -1
- package/dist/esm/website/engine-frontend-website-provider-registry.js +5 -1
- package/dist/esm/website/engine-frontend-website-provider-registry.js.map +1 -1
- package/dist/esm/website/frontend-website-provider-module.types.d.ts +63 -3
- package/dist/esm/website/frontend-website-provider-module.types.d.ts.map +1 -1
- package/dist/esm/website/frontend-website-provider-module.types.js +7 -2
- package/dist/esm/website/frontend-website-provider-module.types.js.map +1 -1
- package/dist/esm/website/index.d.ts +4 -0
- package/dist/esm/website/index.d.ts.map +1 -1
- package/dist/esm/website/index.js +4 -0
- package/dist/esm/website/index.js.map +1 -1
- package/dist/tsconfig.build.tsbuildinfo +1 -1
- package/package.json +15 -3
|
@@ -1,13 +1,24 @@
|
|
|
1
|
-
import {
|
|
1
|
+
import { ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME } from '../../engine-frontend-providers-package.js';
|
|
2
|
+
import { ProviderDeploymentModel, BUILTIN_PROVIDER_CAPABILITY, BUILTIN_PROVIDER_PROTOCOL, defineProviderMetadata, ENGINE_PROVIDER_ORIGIN, ProviderTier } from '@wildo-ai/saas-models/public-runtime';
|
|
2
3
|
export const MicrosoftFrontendAppProvider = {
|
|
3
|
-
metadata: {
|
|
4
|
+
metadata: defineProviderMetadata({
|
|
4
5
|
ref: 'microsoft',
|
|
5
|
-
|
|
6
|
-
|
|
6
|
+
packageName: ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME,
|
|
7
|
+
tier: ProviderTier.MAIN,
|
|
8
|
+
origin: ENGINE_PROVIDER_ORIGIN,
|
|
9
|
+
}),
|
|
7
10
|
providerCapabilities: [BUILTIN_PROVIDER_CAPABILITY.SSO_OAUTH2],
|
|
8
11
|
protocols: [BUILTIN_PROVIDER_PROTOCOL.SSO_OAUTH2],
|
|
9
12
|
publicConfig: {
|
|
10
13
|
authProviderRef: 'microsoft',
|
|
11
14
|
},
|
|
15
|
+
/**
|
|
16
|
+
* Mirrors the authored `microsoft` BACKEND profile.
|
|
17
|
+
*/
|
|
18
|
+
complianceProfile: {
|
|
19
|
+
deploymentModels: [ProviderDeploymentModel.VENDOR_HOSTED],
|
|
20
|
+
processingRegions: ['us-east-1', 'eu-west-1'],
|
|
21
|
+
vendorLegalEntityName: 'Microsoft Corporation',
|
|
22
|
+
},
|
|
12
23
|
};
|
|
13
24
|
//# sourceMappingURL=microsoft.frontend-app.module.js.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"microsoft.frontend-app.module.js","sourceRoot":"","sources":["../../../../../src/providers/microsoft/microsoft.frontend-app.module.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,
|
|
1
|
+
{"version":3,"file":"microsoft.frontend-app.module.js","sourceRoot":"","sources":["../../../../../src/providers/microsoft/microsoft.frontend-app.module.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,sCAAsC,EAAE,MAAM,yCAAyC,CAAC;AACjG,OAAO,EACL,uBAAuB,EAAE,2BAA2B,EAAE,yBAAyB,EAAE,sBAAsB,EAAE,sBAAsB,EAAE,YAAY,EAAE,MAAM,sCAAsC,CAAC;AAG9L,MAAM,CAAC,MAAM,4BAA4B,GAA8B;IACrE,QAAQ,EAAE,sBAAsB,CAAC;QAC/B,GAAG,EAAE,WAAW;QAChB,WAAW,EAAE,sCAAsC;QACnD,IAAI,EAAE,YAAY,CAAC,IAAI;QACvB,MAAM,EAAE,sBAAsB;KAC/B,CAAC;IACF,oBAAoB,EAAE,CAAC,2BAA2B,CAAC,UAAU,CAAC;IAC9D,SAAS,EAAE,CAAC,yBAAyB,CAAC,UAAU,CAAC;IACjD,YAAY,EAAE;QACZ,eAAe,EAAE,WAAW;KAC7B;IACD;;OAEG;IACH,iBAAiB,EAAE;QACjB,gBAAgB,EAAE,CAAC,uBAAuB,CAAC,aAAa,CAAC;QACzD,iBAAiB,EAAE,CAAC,WAAW,EAAE,WAAW,CAAC;QAC7C,qBAAqB,EAAE,uBAAuB;KAC/C;CACF,CAAC","sourcesContent":["import { ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME } from '../../engine-frontend-providers-package';\nimport {\n ProviderDeploymentModel, BUILTIN_PROVIDER_CAPABILITY, BUILTIN_PROVIDER_PROTOCOL, defineProviderMetadata, ENGINE_PROVIDER_ORIGIN, ProviderTier } from '@wildo-ai/saas-models/public-runtime';\nimport type { FrontendAppProviderModule } from '../../app/frontend-app-provider-module.types';\n\nexport const MicrosoftFrontendAppProvider: FrontendAppProviderModule = {\n metadata: defineProviderMetadata({\n ref: 'microsoft',\n packageName: ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME,\n tier: ProviderTier.MAIN,\n origin: ENGINE_PROVIDER_ORIGIN,\n }),\n providerCapabilities: [BUILTIN_PROVIDER_CAPABILITY.SSO_OAUTH2],\n protocols: [BUILTIN_PROVIDER_PROTOCOL.SSO_OAUTH2],\n publicConfig: {\n authProviderRef: 'microsoft',\n },\n /**\n * Mirrors the authored `microsoft` BACKEND profile.\n */\n complianceProfile: {\n deploymentModels: [ProviderDeploymentModel.VENDOR_HOSTED],\n processingRegions: ['us-east-1', 'eu-west-1'],\n vendorLegalEntityName: 'Microsoft Corporation',\n },\n};\n"]}
|
|
@@ -1,3 +1,22 @@
|
|
|
1
1
|
import type { FrontendWebsiteProviderModule } from '../../website/frontend-website-provider-module.types';
|
|
2
|
+
/**
|
|
3
|
+
* PostHog product analytics for the marketing website.
|
|
4
|
+
*
|
|
5
|
+
* Like Sentry beside it, this declared `FRONTEND_SDK` and loaded nothing until
|
|
6
|
+
* #332 — the website resolved its ref into a `data-*` attribute and stopped.
|
|
7
|
+
*
|
|
8
|
+
* ## Why `apiHost` is a DERIVED origin and not a listed one
|
|
9
|
+
*
|
|
10
|
+
* PostHog's ingest host is configuration: a region (`us`/`eu`), a reverse proxy
|
|
11
|
+
* on the application's own domain — the vendor recommends one, so it is common
|
|
12
|
+
* — or a self-hosted deployment. Listing hostnames here would be a guess about
|
|
13
|
+
* the application's infrastructure that is wrong for every one of those cases,
|
|
14
|
+
* and wrong in production only, because development is report-only.
|
|
15
|
+
*
|
|
16
|
+
* So the module says WHERE the origin is and the CLI reads it out of the
|
|
17
|
+
* application's own `publicConfig.apiHost` when composing that service's policy.
|
|
18
|
+
* Absent, it contributes nothing — which is correct: a website that has not
|
|
19
|
+
* configured PostHog needs no origin for it.
|
|
20
|
+
*/
|
|
2
21
|
export declare const PostHogFrontendWebsiteProvider: FrontendWebsiteProviderModule;
|
|
3
22
|
//# sourceMappingURL=posthog.frontend-website.module.d.ts.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"posthog.frontend-website.module.d.ts","sourceRoot":"","sources":["../../../../../src/providers/posthog/posthog.frontend-website.module.ts"],"names":[],"mappings":"
|
|
1
|
+
{"version":3,"file":"posthog.frontend-website.module.d.ts","sourceRoot":"","sources":["../../../../../src/providers/posthog/posthog.frontend-website.module.ts"],"names":[],"mappings":"AAUA,OAAO,KAAK,EAAE,6BAA6B,EAAE,MAAM,sDAAsD,CAAC;AAE1G;;;;;;;;;;;;;;;;;;GAkBG;AACH,eAAO,MAAM,8BAA8B,EAAE,6BAwD5C,CAAC"}
|
|
@@ -1,14 +1,75 @@
|
|
|
1
|
-
import {
|
|
1
|
+
import { ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME } from '../../engine-frontend-providers-package.js';
|
|
2
|
+
import { ProviderDeploymentModel, BUILTIN_PROVIDER_CAPABILITY, BUILTIN_PROVIDER_PROTOCOL, ProviderFrontendCspOriginBucket, ProviderTier, defineProviderMetadata, ENGINE_PROVIDER_ORIGIN, } from '@wildo-ai/saas-models/public-runtime';
|
|
3
|
+
/**
|
|
4
|
+
* PostHog product analytics for the marketing website.
|
|
5
|
+
*
|
|
6
|
+
* Like Sentry beside it, this declared `FRONTEND_SDK` and loaded nothing until
|
|
7
|
+
* #332 — the website resolved its ref into a `data-*` attribute and stopped.
|
|
8
|
+
*
|
|
9
|
+
* ## Why `apiHost` is a DERIVED origin and not a listed one
|
|
10
|
+
*
|
|
11
|
+
* PostHog's ingest host is configuration: a region (`us`/`eu`), a reverse proxy
|
|
12
|
+
* on the application's own domain — the vendor recommends one, so it is common
|
|
13
|
+
* — or a self-hosted deployment. Listing hostnames here would be a guess about
|
|
14
|
+
* the application's infrastructure that is wrong for every one of those cases,
|
|
15
|
+
* and wrong in production only, because development is report-only.
|
|
16
|
+
*
|
|
17
|
+
* So the module says WHERE the origin is and the CLI reads it out of the
|
|
18
|
+
* application's own `publicConfig.apiHost` when composing that service's policy.
|
|
19
|
+
* Absent, it contributes nothing — which is correct: a website that has not
|
|
20
|
+
* configured PostHog needs no origin for it.
|
|
21
|
+
*/
|
|
2
22
|
export const PostHogFrontendWebsiteProvider = {
|
|
3
|
-
metadata: {
|
|
23
|
+
metadata: defineProviderMetadata({
|
|
4
24
|
ref: 'posthog',
|
|
5
|
-
|
|
6
|
-
|
|
25
|
+
packageName: ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME,
|
|
26
|
+
tier: ProviderTier.MAIN,
|
|
27
|
+
origin: ENGINE_PROVIDER_ORIGIN,
|
|
28
|
+
}),
|
|
7
29
|
providerCapabilities: [BUILTIN_PROVIDER_CAPABILITY.FRONTEND_PRODUCT_ANALYTICS],
|
|
8
30
|
protocols: [BUILTIN_PROVIDER_PROTOCOL.FRONTEND_SDK],
|
|
9
31
|
publicConfig: {
|
|
10
32
|
integrationKind: 'product-analytics',
|
|
11
33
|
websiteRuntime: true,
|
|
12
34
|
},
|
|
35
|
+
csp: {
|
|
36
|
+
derivedOrigins: [
|
|
37
|
+
{ publicConfigKey: 'apiHost', bucket: ProviderFrontendCspOriginBucket.CONNECT },
|
|
38
|
+
],
|
|
39
|
+
},
|
|
40
|
+
sdk: {
|
|
41
|
+
descriptor: { packageName: 'posthog-js' },
|
|
42
|
+
async activate({ providerRef, publicConfig }) {
|
|
43
|
+
const apiKey = publicConfig.apiKey;
|
|
44
|
+
if (typeof apiKey !== 'string' || apiKey.length === 0) {
|
|
45
|
+
throw new Error(`Provider "${providerRef}" needs a PostHog project API key in its publicConfig.apiKey. Without one `
|
|
46
|
+
+ 'the SDK starts and captures nothing, which is indistinguishable from a site nobody visits. Supply '
|
|
47
|
+
+ "it by mapping this provider's contribution in the application's own provider-contributions.");
|
|
48
|
+
}
|
|
49
|
+
const apiHost = publicConfig.apiHost;
|
|
50
|
+
// DYNAMIC on purpose: `posthog-js` is a declared OPTIONAL peer of this
|
|
51
|
+
// package, so it becomes its own chunk and only a surface that turns
|
|
52
|
+
// analytics on pays for it.
|
|
53
|
+
const { default: posthog } = await import('posthog-js');
|
|
54
|
+
posthog.init(apiKey, typeof apiHost === 'string' ? { api_host: apiHost } : {});
|
|
55
|
+
return {
|
|
56
|
+
handle: posthog,
|
|
57
|
+
// PostHog has no full shutdown; opting out is the strongest stop it
|
|
58
|
+
// offers, and it is the one a consent withdrawal actually needs.
|
|
59
|
+
deactivate: () => {
|
|
60
|
+
posthog.opt_out_capturing();
|
|
61
|
+
},
|
|
62
|
+
};
|
|
63
|
+
},
|
|
64
|
+
},
|
|
65
|
+
/**
|
|
66
|
+
* Mirrors the authored `posthog` BACKEND profile. The browser SDK ingests to the same US or EU
|
|
67
|
+
* cloud the backend provider names, so the region set is the operator's one choice.
|
|
68
|
+
*/
|
|
69
|
+
complianceProfile: {
|
|
70
|
+
deploymentModels: [ProviderDeploymentModel.VENDOR_HOSTED],
|
|
71
|
+
processingRegions: ['us-east-1', 'eu-central-1'],
|
|
72
|
+
vendorLegalEntityName: 'PostHog, Inc.',
|
|
73
|
+
},
|
|
13
74
|
};
|
|
14
75
|
//# sourceMappingURL=posthog.frontend-website.module.js.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"posthog.frontend-website.module.js","sourceRoot":"","sources":["../../../../../src/providers/posthog/posthog.frontend-website.module.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,EAC3B,yBAAyB,EACzB,
|
|
1
|
+
{"version":3,"file":"posthog.frontend-website.module.js","sourceRoot":"","sources":["../../../../../src/providers/posthog/posthog.frontend-website.module.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,sCAAsC,EAAE,MAAM,yCAAyC,CAAC;AACjG,OAAO,EACL,uBAAuB,EACvB,2BAA2B,EAC3B,yBAAyB,EACzB,+BAA+B,EAC/B,YAAY,EACZ,sBAAsB,EACtB,sBAAsB,GACvB,MAAM,sCAAsC,CAAC;AAG9C;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,CAAC,MAAM,8BAA8B,GAAkC;IAC3E,QAAQ,EAAE,sBAAsB,CAAC;QAC/B,GAAG,EAAE,SAAS;QACd,WAAW,EAAE,sCAAsC;QACnD,IAAI,EAAE,YAAY,CAAC,IAAI;QACvB,MAAM,EAAE,sBAAsB;KAC/B,CAAC;IACF,oBAAoB,EAAE,CAAC,2BAA2B,CAAC,0BAA0B,CAAC;IAC9E,SAAS,EAAE,CAAC,yBAAyB,CAAC,YAAY,CAAC;IACnD,YAAY,EAAE;QACZ,eAAe,EAAE,mBAAmB;QACpC,cAAc,EAAE,IAAI;KACrB;IACD,GAAG,EAAE;QACH,cAAc,EAAE;YACd,EAAE,eAAe,EAAE,SAAS,EAAE,MAAM,EAAE,+BAA+B,CAAC,OAAO,EAAE;SAChF;KACF;IACD,GAAG,EAAE;QACH,UAAU,EAAE,EAAE,WAAW,EAAE,YAAY,EAAE;QACzC,KAAK,CAAC,QAAQ,CAAC,EAAE,WAAW,EAAE,YAAY,EAAE;YAC1C,MAAM,MAAM,GAAG,YAAY,CAAC,MAAM,CAAC;YACnC,IAAI,OAAO,MAAM,KAAK,QAAQ,IAAI,MAAM,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;gBACtD,MAAM,IAAI,KAAK,CACb,aAAa,WAAW,4EAA4E;sBAClG,oGAAoG;sBACpG,6FAA6F,CAChG,CAAC;YACJ,CAAC;YACD,MAAM,OAAO,GAAG,YAAY,CAAC,OAAO,CAAC;YAErC,uEAAuE;YACvE,qEAAqE;YACrE,4BAA4B;YAC5B,MAAM,EAAE,OAAO,EAAE,OAAO,EAAE,GAAG,MAAM,MAAM,CAAC,YAAY,CAAC,CAAC;YACxD,OAAO,CAAC,IAAI,CAAC,MAAM,EAAE,OAAO,OAAO,KAAK,QAAQ,CAAC,CAAC,CAAC,EAAE,QAAQ,EAAE,OAAO,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC;YAE/E,OAAO;gBACL,MAAM,EAAE,OAAO;gBACf,oEAAoE;gBACpE,iEAAiE;gBACjE,UAAU,EAAE,GAAG,EAAE;oBACf,OAAO,CAAC,iBAAiB,EAAE,CAAC;gBAC9B,CAAC;aACF,CAAC;QACJ,CAAC;KACF;IACD;;;OAGG;IACH,iBAAiB,EAAE;QACjB,gBAAgB,EAAE,CAAC,uBAAuB,CAAC,aAAa,CAAC;QACzD,iBAAiB,EAAE,CAAC,WAAW,EAAE,cAAc,CAAC;QAChD,qBAAqB,EAAE,eAAe;KACvC;CACF,CAAC","sourcesContent":["import { ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME } from '../../engine-frontend-providers-package';\nimport {\n ProviderDeploymentModel,\n BUILTIN_PROVIDER_CAPABILITY,\n BUILTIN_PROVIDER_PROTOCOL,\n ProviderFrontendCspOriginBucket,\n ProviderTier,\n defineProviderMetadata,\n ENGINE_PROVIDER_ORIGIN,\n} from '@wildo-ai/saas-models/public-runtime';\nimport type { FrontendWebsiteProviderModule } from '../../website/frontend-website-provider-module.types';\n\n/**\n * PostHog product analytics for the marketing website.\n *\n * Like Sentry beside it, this declared `FRONTEND_SDK` and loaded nothing until\n * #332 — the website resolved its ref into a `data-*` attribute and stopped.\n *\n * ## Why `apiHost` is a DERIVED origin and not a listed one\n *\n * PostHog's ingest host is configuration: a region (`us`/`eu`), a reverse proxy\n * on the application's own domain — the vendor recommends one, so it is common\n * — or a self-hosted deployment. Listing hostnames here would be a guess about\n * the application's infrastructure that is wrong for every one of those cases,\n * and wrong in production only, because development is report-only.\n *\n * So the module says WHERE the origin is and the CLI reads it out of the\n * application's own `publicConfig.apiHost` when composing that service's policy.\n * Absent, it contributes nothing — which is correct: a website that has not\n * configured PostHog needs no origin for it.\n */\nexport const PostHogFrontendWebsiteProvider: FrontendWebsiteProviderModule = {\n metadata: defineProviderMetadata({\n ref: 'posthog',\n packageName: ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME,\n tier: ProviderTier.MAIN,\n origin: ENGINE_PROVIDER_ORIGIN,\n }),\n providerCapabilities: [BUILTIN_PROVIDER_CAPABILITY.FRONTEND_PRODUCT_ANALYTICS],\n protocols: [BUILTIN_PROVIDER_PROTOCOL.FRONTEND_SDK],\n publicConfig: {\n integrationKind: 'product-analytics',\n websiteRuntime: true,\n },\n csp: {\n derivedOrigins: [\n { publicConfigKey: 'apiHost', bucket: ProviderFrontendCspOriginBucket.CONNECT },\n ],\n },\n sdk: {\n descriptor: { packageName: 'posthog-js' },\n async activate({ providerRef, publicConfig }) {\n const apiKey = publicConfig.apiKey;\n if (typeof apiKey !== 'string' || apiKey.length === 0) {\n throw new Error(\n `Provider \"${providerRef}\" needs a PostHog project API key in its publicConfig.apiKey. Without one `\n + 'the SDK starts and captures nothing, which is indistinguishable from a site nobody visits. Supply '\n + \"it by mapping this provider's contribution in the application's own provider-contributions.\",\n );\n }\n const apiHost = publicConfig.apiHost;\n\n // DYNAMIC on purpose: `posthog-js` is a declared OPTIONAL peer of this\n // package, so it becomes its own chunk and only a surface that turns\n // analytics on pays for it.\n const { default: posthog } = await import('posthog-js');\n posthog.init(apiKey, typeof apiHost === 'string' ? { api_host: apiHost } : {});\n\n return {\n handle: posthog,\n // PostHog has no full shutdown; opting out is the strongest stop it\n // offers, and it is the one a consent withdrawal actually needs.\n deactivate: () => {\n posthog.opt_out_capturing();\n },\n };\n },\n },\n /**\n * Mirrors the authored `posthog` BACKEND profile. The browser SDK ingests to the same US or EU\n * cloud the backend provider names, so the region set is the operator's one choice.\n */\n complianceProfile: {\n deploymentModels: [ProviderDeploymentModel.VENDOR_HOSTED],\n processingRegions: ['us-east-1', 'eu-central-1'],\n vendorLegalEntityName: 'PostHog, Inc.',\n },\n};\n"]}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"recaptcha.frontend-website.module.d.ts","sourceRoot":"","sources":["../../../../../src/providers/recaptcha/recaptcha.frontend-website.module.ts"],"names":[],"mappings":"
|
|
1
|
+
{"version":3,"file":"recaptcha.frontend-website.module.d.ts","sourceRoot":"","sources":["../../../../../src/providers/recaptcha/recaptcha.frontend-website.module.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,6BAA6B,EAAE,MAAM,sDAAsD,CAAC;AAE1G,eAAO,MAAM,gCAAgC,EAAE,6BA8B9C,CAAC"}
|
|
@@ -1,14 +1,34 @@
|
|
|
1
|
-
import {
|
|
1
|
+
import { ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME } from '../../engine-frontend-providers-package.js';
|
|
2
|
+
import { ProviderDeploymentModel, BUILTIN_PROVIDER_CAPABILITY, BUILTIN_PROVIDER_PROTOCOL, defineProviderMetadata, ENGINE_PROVIDER_ORIGIN, ProviderTier } from '@wildo-ai/saas-models/public-runtime';
|
|
2
3
|
export const RecaptchaFrontendWebsiteProvider = {
|
|
3
|
-
metadata: {
|
|
4
|
+
metadata: defineProviderMetadata({
|
|
4
5
|
ref: 'recaptcha',
|
|
5
|
-
|
|
6
|
-
|
|
6
|
+
packageName: ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME,
|
|
7
|
+
tier: ProviderTier.CATALOGUE,
|
|
8
|
+
origin: ENGINE_PROVIDER_ORIGIN,
|
|
9
|
+
}),
|
|
7
10
|
providerCapabilities: [BUILTIN_PROVIDER_CAPABILITY.FRONTEND_CAPTCHA],
|
|
8
11
|
protocols: [BUILTIN_PROVIDER_PROTOCOL.FRONTEND_SDK],
|
|
9
12
|
publicConfig: {
|
|
10
13
|
integrationKind: 'captcha',
|
|
11
14
|
websiteRuntime: true,
|
|
12
15
|
},
|
|
16
|
+
/**
|
|
17
|
+
* Researched 2026-09-06, and the entity is deliberately NOT `Google LLC`.
|
|
18
|
+
*
|
|
19
|
+
* Google's role for reCAPTCHA changed from data CONTROLLER to data PROCESSOR on 2 April 2026.
|
|
20
|
+
* Under the current terms the website operator is the controller and `Google Ireland Limited` is
|
|
21
|
+
* the named processor for the EEA, with processing still reaching US servers under standard
|
|
22
|
+
* contractual clauses. The sibling `google` provider carries `Google LLC` — same corporate group,
|
|
23
|
+
* different contracting entity for this service, which is why the two refs are separate.
|
|
24
|
+
*
|
|
25
|
+
* `global` is the honest region: classic reCAPTCHA offers the operator NO data-residency choice,
|
|
26
|
+
* so naming a datacentre would invent a decision nobody gets to make.
|
|
27
|
+
*/
|
|
28
|
+
complianceProfile: {
|
|
29
|
+
deploymentModels: [ProviderDeploymentModel.VENDOR_HOSTED],
|
|
30
|
+
processingRegions: ['global'],
|
|
31
|
+
vendorLegalEntityName: 'Google Ireland Limited',
|
|
32
|
+
},
|
|
13
33
|
};
|
|
14
34
|
//# sourceMappingURL=recaptcha.frontend-website.module.js.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"recaptcha.frontend-website.module.js","sourceRoot":"","sources":["../../../../../src/providers/recaptcha/recaptcha.frontend-website.module.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,2BAA2B,
|
|
1
|
+
{"version":3,"file":"recaptcha.frontend-website.module.js","sourceRoot":"","sources":["../../../../../src/providers/recaptcha/recaptcha.frontend-website.module.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,sCAAsC,EAAE,MAAM,yCAAyC,CAAC;AACjG,OAAO,EACL,uBAAuB,EAAE,2BAA2B,EAAE,yBAAyB,EAAE,sBAAsB,EAAE,sBAAsB,EAAE,YAAY,EAAE,MAAM,sCAAsC,CAAC;AAG9L,MAAM,CAAC,MAAM,gCAAgC,GAAkC;IAC7E,QAAQ,EAAE,sBAAsB,CAAC;QAC/B,GAAG,EAAE,WAAW;QAChB,WAAW,EAAE,sCAAsC;QACnD,IAAI,EAAE,YAAY,CAAC,SAAS;QAC5B,MAAM,EAAE,sBAAsB;KAC/B,CAAC;IACF,oBAAoB,EAAE,CAAC,2BAA2B,CAAC,gBAAgB,CAAC;IACpE,SAAS,EAAE,CAAC,yBAAyB,CAAC,YAAY,CAAC;IACnD,YAAY,EAAE;QACZ,eAAe,EAAE,SAAS;QAC1B,cAAc,EAAE,IAAI;KACrB;IACD;;;;;;;;;;;OAWG;IACH,iBAAiB,EAAE;QACjB,gBAAgB,EAAE,CAAC,uBAAuB,CAAC,aAAa,CAAC;QACzD,iBAAiB,EAAE,CAAC,QAAQ,CAAC;QAC7B,qBAAqB,EAAE,wBAAwB;KAChD;CACF,CAAC","sourcesContent":["import { ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME } from '../../engine-frontend-providers-package';\nimport {\n ProviderDeploymentModel, BUILTIN_PROVIDER_CAPABILITY, BUILTIN_PROVIDER_PROTOCOL, defineProviderMetadata, ENGINE_PROVIDER_ORIGIN, ProviderTier } from '@wildo-ai/saas-models/public-runtime';\nimport type { FrontendWebsiteProviderModule } from '../../website/frontend-website-provider-module.types';\n\nexport const RecaptchaFrontendWebsiteProvider: FrontendWebsiteProviderModule = {\n metadata: defineProviderMetadata({\n ref: 'recaptcha',\n packageName: ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME,\n tier: ProviderTier.CATALOGUE,\n origin: ENGINE_PROVIDER_ORIGIN,\n }),\n providerCapabilities: [BUILTIN_PROVIDER_CAPABILITY.FRONTEND_CAPTCHA],\n protocols: [BUILTIN_PROVIDER_PROTOCOL.FRONTEND_SDK],\n publicConfig: {\n integrationKind: 'captcha',\n websiteRuntime: true,\n },\n /**\n * Researched 2026-09-06, and the entity is deliberately NOT `Google LLC`.\n *\n * Google's role for reCAPTCHA changed from data CONTROLLER to data PROCESSOR on 2 April 2026.\n * Under the current terms the website operator is the controller and `Google Ireland Limited` is\n * the named processor for the EEA, with processing still reaching US servers under standard\n * contractual clauses. The sibling `google` provider carries `Google LLC` — same corporate group,\n * different contracting entity for this service, which is why the two refs are separate.\n *\n * `global` is the honest region: classic reCAPTCHA offers the operator NO data-residency choice,\n * so naming a datacentre would invent a decision nobody gets to make.\n */\n complianceProfile: {\n deploymentModels: [ProviderDeploymentModel.VENDOR_HOSTED],\n processingRegions: ['global'],\n vendorLegalEntityName: 'Google Ireland Limited',\n },\n};\n"]}
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../../../src/providers/sentry/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,6BAA6B,EAAE,MAAM,kCAAkC,CAAC"}
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../../../src/providers/sentry/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,6BAA6B,EAAE,MAAM,kCAAkC,CAAC","sourcesContent":["export { SentryFrontendWebsiteProvider } from './sentry.frontend-website.module';\n"]}
|
|
@@ -0,0 +1,57 @@
|
|
|
1
|
+
import type { FrontendAppProviderModule } from '../../app/frontend-app-provider-module.types';
|
|
2
|
+
/**
|
|
3
|
+
* Sentry browser error monitoring for the SaaS APPLICATION frontend.
|
|
4
|
+
*
|
|
5
|
+
* Sibling of `sentry.frontend-website.module.ts`, and the two are deliberately
|
|
6
|
+
* separate modules rather than one shared object with a surface flag: the website's
|
|
7
|
+
* job is finished once `Sentry.init` installs the vendor's global handlers, and this
|
|
8
|
+
* one's is not — see below. They also carry different capabilities in an
|
|
9
|
+
* application's config (`services.website.providers` vs `services.app.providers`),
|
|
10
|
+
* so a deployment can monitor one and not the other.
|
|
11
|
+
*
|
|
12
|
+
* ## Why an SDK alone would report nothing that matters here (#437)
|
|
13
|
+
*
|
|
14
|
+
* `Sentry.init` hooks `window.onerror` and `unhandledrejection`. A React ERROR
|
|
15
|
+
* BOUNDARY catches the error before either fires — that is what a boundary is — so
|
|
16
|
+
* on a surface built out of boundaries the vendor's global handlers see the
|
|
17
|
+
* accidents and miss the crashes. Wildo's application frontend catches every render
|
|
18
|
+
* error in `ErrorBoundary`, `RouterErrorBoundary` and `error-management`, and each
|
|
19
|
+
* publishes `ERROR_OCCURED`.
|
|
20
|
+
*
|
|
21
|
+
* So this module's real contract is not `init` — it is the
|
|
22
|
+
* `FrontendErrorMonitoringSink` it returns as its handle. The framework's bridge
|
|
23
|
+
* subscribes to that bus once and calls `reportCrash`; this module translates the
|
|
24
|
+
* framework's report into `captureException`. The vendor's global handlers stay
|
|
25
|
+
* installed and still catch what escapes a boundary entirely.
|
|
26
|
+
*
|
|
27
|
+
* ## What is NOT enabled, and why nothing is set to disable it
|
|
28
|
+
*
|
|
29
|
+
* No `sendDefaultPii`, no `dataCollection`. Sentry's conservative posture is the
|
|
30
|
+
* DEFAULT — with neither set the browser SDK sends no cookies, no user identity
|
|
31
|
+
* fields, no IP address and no request bodies — so the correct action is to set
|
|
32
|
+
* nothing rather than to set a flag `false`. `sendDefaultPii` is additionally
|
|
33
|
+
* deprecated from SDK 10.54.0 in favour of `dataCollection`, and this repository
|
|
34
|
+
* pins `@sentry/browser` at 10.73.0, so writing it would ship a deprecated option to
|
|
35
|
+
* achieve a default.
|
|
36
|
+
* spec-cite: Sentry JavaScript SDK docs, "Data Collected"
|
|
37
|
+
* (https://docs.sentry.io/platforms/javascript/data-management/data-collected/),
|
|
38
|
+
* read 2026-09-08.
|
|
39
|
+
*
|
|
40
|
+
* The residual is stated rather than assumed away: even at that default the browser
|
|
41
|
+
* SDK attaches the page URL INCLUDING ITS QUERY STRING, the referrer, and recent
|
|
42
|
+
* console output as breadcrumbs. An application whose URLs carry identifiers is
|
|
43
|
+
* sending them here, and that is a property of the vendor rather than of this
|
|
44
|
+
* module. It is the reason `FRONTEND_ERROR_MONITORING` is a capability an
|
|
45
|
+
* application opts into per environment, not a framework default.
|
|
46
|
+
*
|
|
47
|
+
* ## The DSN, and why the CSP origin is DERIVED
|
|
48
|
+
*
|
|
49
|
+
* Identical to the website module's reasoning: a DSN is per application and often
|
|
50
|
+
* per environment (`https://<key>@o0.ingest.<region>.sentry.io/<id>`), so no static
|
|
51
|
+
* origin list on this module could contain it, and listing a vendor's public ingest
|
|
52
|
+
* hosts would be a guess that is wrong for every self-hosted Sentry. The module
|
|
53
|
+
* declares WHERE the origin lives; the CLI reads it out of `publicConfig.dsn` when
|
|
54
|
+
* it composes the service's policy.
|
|
55
|
+
*/
|
|
56
|
+
export declare const SentryFrontendAppProvider: FrontendAppProviderModule;
|
|
57
|
+
//# sourceMappingURL=sentry.frontend-app.module.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"sentry.frontend-app.module.d.ts","sourceRoot":"","sources":["../../../../../src/providers/sentry/sentry.frontend-app.module.ts"],"names":[],"mappings":"AAYA,OAAO,KAAK,EAAE,yBAAyB,EAAE,MAAM,8CAA8C,CAAC;AAE9F;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqDG;AACH,eAAO,MAAM,yBAAyB,EAAE,yBA0FvC,CAAC"}
|
|
@@ -0,0 +1,141 @@
|
|
|
1
|
+
import { ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME } from '../../engine-frontend-providers-package.js';
|
|
2
|
+
import { ProviderDeploymentModel, BUILTIN_PROVIDER_CAPABILITY, BUILTIN_PROVIDER_PROTOCOL, ProviderFrontendCspOriginBucket, ProviderTier, defineProviderMetadata, ENGINE_PROVIDER_ORIGIN, } from '@wildo-ai/saas-models/public-runtime';
|
|
3
|
+
/**
|
|
4
|
+
* Sentry browser error monitoring for the SaaS APPLICATION frontend.
|
|
5
|
+
*
|
|
6
|
+
* Sibling of `sentry.frontend-website.module.ts`, and the two are deliberately
|
|
7
|
+
* separate modules rather than one shared object with a surface flag: the website's
|
|
8
|
+
* job is finished once `Sentry.init` installs the vendor's global handlers, and this
|
|
9
|
+
* one's is not — see below. They also carry different capabilities in an
|
|
10
|
+
* application's config (`services.website.providers` vs `services.app.providers`),
|
|
11
|
+
* so a deployment can monitor one and not the other.
|
|
12
|
+
*
|
|
13
|
+
* ## Why an SDK alone would report nothing that matters here (#437)
|
|
14
|
+
*
|
|
15
|
+
* `Sentry.init` hooks `window.onerror` and `unhandledrejection`. A React ERROR
|
|
16
|
+
* BOUNDARY catches the error before either fires — that is what a boundary is — so
|
|
17
|
+
* on a surface built out of boundaries the vendor's global handlers see the
|
|
18
|
+
* accidents and miss the crashes. Wildo's application frontend catches every render
|
|
19
|
+
* error in `ErrorBoundary`, `RouterErrorBoundary` and `error-management`, and each
|
|
20
|
+
* publishes `ERROR_OCCURED`.
|
|
21
|
+
*
|
|
22
|
+
* So this module's real contract is not `init` — it is the
|
|
23
|
+
* `FrontendErrorMonitoringSink` it returns as its handle. The framework's bridge
|
|
24
|
+
* subscribes to that bus once and calls `reportCrash`; this module translates the
|
|
25
|
+
* framework's report into `captureException`. The vendor's global handlers stay
|
|
26
|
+
* installed and still catch what escapes a boundary entirely.
|
|
27
|
+
*
|
|
28
|
+
* ## What is NOT enabled, and why nothing is set to disable it
|
|
29
|
+
*
|
|
30
|
+
* No `sendDefaultPii`, no `dataCollection`. Sentry's conservative posture is the
|
|
31
|
+
* DEFAULT — with neither set the browser SDK sends no cookies, no user identity
|
|
32
|
+
* fields, no IP address and no request bodies — so the correct action is to set
|
|
33
|
+
* nothing rather than to set a flag `false`. `sendDefaultPii` is additionally
|
|
34
|
+
* deprecated from SDK 10.54.0 in favour of `dataCollection`, and this repository
|
|
35
|
+
* pins `@sentry/browser` at 10.73.0, so writing it would ship a deprecated option to
|
|
36
|
+
* achieve a default.
|
|
37
|
+
* spec-cite: Sentry JavaScript SDK docs, "Data Collected"
|
|
38
|
+
* (https://docs.sentry.io/platforms/javascript/data-management/data-collected/),
|
|
39
|
+
* read 2026-09-08.
|
|
40
|
+
*
|
|
41
|
+
* The residual is stated rather than assumed away: even at that default the browser
|
|
42
|
+
* SDK attaches the page URL INCLUDING ITS QUERY STRING, the referrer, and recent
|
|
43
|
+
* console output as breadcrumbs. An application whose URLs carry identifiers is
|
|
44
|
+
* sending them here, and that is a property of the vendor rather than of this
|
|
45
|
+
* module. It is the reason `FRONTEND_ERROR_MONITORING` is a capability an
|
|
46
|
+
* application opts into per environment, not a framework default.
|
|
47
|
+
*
|
|
48
|
+
* ## The DSN, and why the CSP origin is DERIVED
|
|
49
|
+
*
|
|
50
|
+
* Identical to the website module's reasoning: a DSN is per application and often
|
|
51
|
+
* per environment (`https://<key>@o0.ingest.<region>.sentry.io/<id>`), so no static
|
|
52
|
+
* origin list on this module could contain it, and listing a vendor's public ingest
|
|
53
|
+
* hosts would be a guess that is wrong for every self-hosted Sentry. The module
|
|
54
|
+
* declares WHERE the origin lives; the CLI reads it out of `publicConfig.dsn` when
|
|
55
|
+
* it composes the service's policy.
|
|
56
|
+
*/
|
|
57
|
+
export const SentryFrontendAppProvider = {
|
|
58
|
+
metadata: defineProviderMetadata({
|
|
59
|
+
ref: 'sentry',
|
|
60
|
+
packageName: ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME,
|
|
61
|
+
tier: ProviderTier.MAIN,
|
|
62
|
+
origin: ENGINE_PROVIDER_ORIGIN,
|
|
63
|
+
}),
|
|
64
|
+
providerCapabilities: [BUILTIN_PROVIDER_CAPABILITY.FRONTEND_ERROR_MONITORING],
|
|
65
|
+
protocols: [BUILTIN_PROVIDER_PROTOCOL.FRONTEND_SDK],
|
|
66
|
+
publicConfig: {
|
|
67
|
+
integrationKind: 'browser-error-monitoring',
|
|
68
|
+
},
|
|
69
|
+
csp: {
|
|
70
|
+
derivedOrigins: [
|
|
71
|
+
{ publicConfigKey: 'dsn', bucket: ProviderFrontendCspOriginBucket.CONNECT },
|
|
72
|
+
],
|
|
73
|
+
},
|
|
74
|
+
sdk: {
|
|
75
|
+
descriptor: { packageName: '@sentry/browser' },
|
|
76
|
+
async activate({ providerRef, publicConfig }) {
|
|
77
|
+
const dsn = publicConfig.dsn;
|
|
78
|
+
if (typeof dsn !== 'string' || dsn.length === 0) {
|
|
79
|
+
throw new Error(`Provider "${providerRef}" needs a Sentry DSN in its publicConfig.dsn. Without one the SDK starts `
|
|
80
|
+
+ 'and reports nothing, which is indistinguishable from a healthy application. Supply it by mapping '
|
|
81
|
+
+ "this provider's contribution in the application's own provider-contributions.");
|
|
82
|
+
}
|
|
83
|
+
// DYNAMIC on purpose: `@sentry/browser` is a declared OPTIONAL peer of this
|
|
84
|
+
// package, so it becomes its own chunk and only an application that turns
|
|
85
|
+
// Sentry on pays for it.
|
|
86
|
+
const Sentry = await import('@sentry/browser');
|
|
87
|
+
const client = Sentry.init({ dsn });
|
|
88
|
+
const sink = {
|
|
89
|
+
reportCrash(report) {
|
|
90
|
+
/*
|
|
91
|
+
* Rebuilt as a real `Error` rather than passed as a plain object, because
|
|
92
|
+
* that is the only shape from which Sentry derives a grouped ISSUE. Given a
|
|
93
|
+
* plain object it records an unhelpful "Non-Error exception captured" with
|
|
94
|
+
* no stack, so every crash in the application would collapse into one
|
|
95
|
+
* issue — which is the same as having none.
|
|
96
|
+
*
|
|
97
|
+
* The stack is transplanted from the report: the error was constructed and
|
|
98
|
+
* thrown somewhere else entirely, and a stack captured HERE would describe
|
|
99
|
+
* this line, in the bridge, on every single crash.
|
|
100
|
+
*/
|
|
101
|
+
const error = new Error(report.message);
|
|
102
|
+
error.name = report.name;
|
|
103
|
+
if (report.stack !== undefined) {
|
|
104
|
+
error.stack = report.stack;
|
|
105
|
+
}
|
|
106
|
+
Sentry.captureException(error, {
|
|
107
|
+
tags: report.tags,
|
|
108
|
+
// React's component stack is not a JavaScript stack and must not be
|
|
109
|
+
// merged into one. As `contexts` it renders as its own labelled block,
|
|
110
|
+
// which is where someone reading the issue looks for "which screen".
|
|
111
|
+
contexts: report.componentStack === undefined
|
|
112
|
+
? undefined
|
|
113
|
+
: { react: { componentStack: report.componentStack } },
|
|
114
|
+
});
|
|
115
|
+
},
|
|
116
|
+
};
|
|
117
|
+
return {
|
|
118
|
+
handle: sink,
|
|
119
|
+
deactivate: async () => {
|
|
120
|
+
await client?.close();
|
|
121
|
+
},
|
|
122
|
+
};
|
|
123
|
+
},
|
|
124
|
+
},
|
|
125
|
+
/**
|
|
126
|
+
* Same vendor, same research as the website module (2026-09-06): legal entity
|
|
127
|
+
* `Functional Software, Inc.` from Sentry's own DPA, and regions given as the
|
|
128
|
+
* vendor's OWN identifiers — the API subdomains `us` (Iowa, `us.sentry.io`) and
|
|
129
|
+
* `de` (Frankfurt, `de.sentry.io`) — rather than mapped onto AWS-style labels,
|
|
130
|
+
* which would be a jurisdiction determination the schema declines to model.
|
|
131
|
+
*
|
|
132
|
+
* Both deployment models, because self-hosted Sentry is a real product and the
|
|
133
|
+
* region is then the operator's own.
|
|
134
|
+
*/
|
|
135
|
+
complianceProfile: {
|
|
136
|
+
deploymentModels: [ProviderDeploymentModel.SELF_HOSTED, ProviderDeploymentModel.VENDOR_HOSTED],
|
|
137
|
+
processingRegions: ['us', 'de'],
|
|
138
|
+
vendorLegalEntityName: 'Functional Software, Inc.',
|
|
139
|
+
},
|
|
140
|
+
};
|
|
141
|
+
//# sourceMappingURL=sentry.frontend-app.module.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"sentry.frontend-app.module.js","sourceRoot":"","sources":["../../../../../src/providers/sentry/sentry.frontend-app.module.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,sCAAsC,EAAE,MAAM,yCAAyC,CAAC;AACjG,OAAO,EACL,uBAAuB,EACvB,2BAA2B,EAC3B,yBAAyB,EACzB,+BAA+B,EAC/B,YAAY,EACZ,sBAAsB,EACtB,sBAAsB,GAGvB,MAAM,sCAAsC,CAAC;AAG9C;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqDG;AACH,MAAM,CAAC,MAAM,yBAAyB,GAA8B;IAClE,QAAQ,EAAE,sBAAsB,CAAC;QAC/B,GAAG,EAAE,QAAQ;QACb,WAAW,EAAE,sCAAsC;QACnD,IAAI,EAAE,YAAY,CAAC,IAAI;QACvB,MAAM,EAAE,sBAAsB;KAC/B,CAAC;IACF,oBAAoB,EAAE,CAAC,2BAA2B,CAAC,yBAAyB,CAAC;IAC7E,SAAS,EAAE,CAAC,yBAAyB,CAAC,YAAY,CAAC;IACnD,YAAY,EAAE;QACZ,eAAe,EAAE,0BAA0B;KAC5C;IACD,GAAG,EAAE;QACH,cAAc,EAAE;YACd,EAAE,eAAe,EAAE,KAAK,EAAE,MAAM,EAAE,+BAA+B,CAAC,OAAO,EAAE;SAC5E;KACF;IACD,GAAG,EAAE;QACH,UAAU,EAAE,EAAE,WAAW,EAAE,iBAAiB,EAAE;QAC9C,KAAK,CAAC,QAAQ,CAAC,EAAE,WAAW,EAAE,YAAY,EAAE;YAC1C,MAAM,GAAG,GAAG,YAAY,CAAC,GAAG,CAAC;YAC7B,IAAI,OAAO,GAAG,KAAK,QAAQ,IAAI,GAAG,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;gBAChD,MAAM,IAAI,KAAK,CACb,aAAa,WAAW,2EAA2E;sBACjG,mGAAmG;sBACnG,+EAA+E,CAClF,CAAC;YACJ,CAAC;YAED,4EAA4E;YAC5E,0EAA0E;YAC1E,yBAAyB;YACzB,MAAM,MAAM,GAAG,MAAM,MAAM,CAAC,iBAAiB,CAAC,CAAC;YAC/C,MAAM,MAAM,GAAG,MAAM,CAAC,IAAI,CAAC,EAAE,GAAG,EAAE,CAAC,CAAC;YAEpC,MAAM,IAAI,GAAgC;gBACxC,WAAW,CAAC,MAA2B;oBACrC;;;;;;;;;;uBAUG;oBACH,MAAM,KAAK,GAAG,IAAI,KAAK,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC;oBACxC,KAAK,CAAC,IAAI,GAAG,MAAM,CAAC,IAAI,CAAC;oBACzB,IAAI,MAAM,CAAC,KAAK,KAAK,SAAS,EAAE,CAAC;wBAC/B,KAAK,CAAC,KAAK,GAAG,MAAM,CAAC,KAAK,CAAC;oBAC7B,CAAC;oBAED,MAAM,CAAC,gBAAgB,CAAC,KAAK,EAAE;wBAC7B,IAAI,EAAE,MAAM,CAAC,IAAI;wBACjB,oEAAoE;wBACpE,uEAAuE;wBACvE,qEAAqE;wBACrE,QAAQ,EACN,MAAM,CAAC,cAAc,KAAK,SAAS;4BACjC,CAAC,CAAC,SAAS;4BACX,CAAC,CAAC,EAAE,KAAK,EAAE,EAAE,cAAc,EAAE,MAAM,CAAC,cAAc,EAAE,EAAE;qBAC3D,CAAC,CAAC;gBACL,CAAC;aACF,CAAC;YAEF,OAAO;gBACL,MAAM,EAAE,IAAI;gBACZ,UAAU,EAAE,KAAK,IAAI,EAAE;oBACrB,MAAM,MAAM,EAAE,KAAK,EAAE,CAAC;gBACxB,CAAC;aACF,CAAC;QACJ,CAAC;KACF;IACD;;;;;;;;;OASG;IACH,iBAAiB,EAAE;QACjB,gBAAgB,EAAE,CAAC,uBAAuB,CAAC,WAAW,EAAE,uBAAuB,CAAC,aAAa,CAAC;QAC9F,iBAAiB,EAAE,CAAC,IAAI,EAAE,IAAI,CAAC;QAC/B,qBAAqB,EAAE,2BAA2B;KACnD;CACF,CAAC","sourcesContent":["import { ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME } from '../../engine-frontend-providers-package';\nimport {\n ProviderDeploymentModel,\n BUILTIN_PROVIDER_CAPABILITY,\n BUILTIN_PROVIDER_PROTOCOL,\n ProviderFrontendCspOriginBucket,\n ProviderTier,\n defineProviderMetadata,\n ENGINE_PROVIDER_ORIGIN,\n type FrontendCrashReport,\n type FrontendErrorMonitoringSink,\n} from '@wildo-ai/saas-models/public-runtime';\nimport type { FrontendAppProviderModule } from '../../app/frontend-app-provider-module.types';\n\n/**\n * Sentry browser error monitoring for the SaaS APPLICATION frontend.\n *\n * Sibling of `sentry.frontend-website.module.ts`, and the two are deliberately\n * separate modules rather than one shared object with a surface flag: the website's\n * job is finished once `Sentry.init` installs the vendor's global handlers, and this\n * one's is not — see below. They also carry different capabilities in an\n * application's config (`services.website.providers` vs `services.app.providers`),\n * so a deployment can monitor one and not the other.\n *\n * ## Why an SDK alone would report nothing that matters here (#437)\n *\n * `Sentry.init` hooks `window.onerror` and `unhandledrejection`. A React ERROR\n * BOUNDARY catches the error before either fires — that is what a boundary is — so\n * on a surface built out of boundaries the vendor's global handlers see the\n * accidents and miss the crashes. Wildo's application frontend catches every render\n * error in `ErrorBoundary`, `RouterErrorBoundary` and `error-management`, and each\n * publishes `ERROR_OCCURED`.\n *\n * So this module's real contract is not `init` — it is the\n * `FrontendErrorMonitoringSink` it returns as its handle. The framework's bridge\n * subscribes to that bus once and calls `reportCrash`; this module translates the\n * framework's report into `captureException`. The vendor's global handlers stay\n * installed and still catch what escapes a boundary entirely.\n *\n * ## What is NOT enabled, and why nothing is set to disable it\n *\n * No `sendDefaultPii`, no `dataCollection`. Sentry's conservative posture is the\n * DEFAULT — with neither set the browser SDK sends no cookies, no user identity\n * fields, no IP address and no request bodies — so the correct action is to set\n * nothing rather than to set a flag `false`. `sendDefaultPii` is additionally\n * deprecated from SDK 10.54.0 in favour of `dataCollection`, and this repository\n * pins `@sentry/browser` at 10.73.0, so writing it would ship a deprecated option to\n * achieve a default.\n * spec-cite: Sentry JavaScript SDK docs, \"Data Collected\"\n * (https://docs.sentry.io/platforms/javascript/data-management/data-collected/),\n * read 2026-09-08.\n *\n * The residual is stated rather than assumed away: even at that default the browser\n * SDK attaches the page URL INCLUDING ITS QUERY STRING, the referrer, and recent\n * console output as breadcrumbs. An application whose URLs carry identifiers is\n * sending them here, and that is a property of the vendor rather than of this\n * module. It is the reason `FRONTEND_ERROR_MONITORING` is a capability an\n * application opts into per environment, not a framework default.\n *\n * ## The DSN, and why the CSP origin is DERIVED\n *\n * Identical to the website module's reasoning: a DSN is per application and often\n * per environment (`https://<key>@o0.ingest.<region>.sentry.io/<id>`), so no static\n * origin list on this module could contain it, and listing a vendor's public ingest\n * hosts would be a guess that is wrong for every self-hosted Sentry. The module\n * declares WHERE the origin lives; the CLI reads it out of `publicConfig.dsn` when\n * it composes the service's policy.\n */\nexport const SentryFrontendAppProvider: FrontendAppProviderModule = {\n metadata: defineProviderMetadata({\n ref: 'sentry',\n packageName: ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME,\n tier: ProviderTier.MAIN,\n origin: ENGINE_PROVIDER_ORIGIN,\n }),\n providerCapabilities: [BUILTIN_PROVIDER_CAPABILITY.FRONTEND_ERROR_MONITORING],\n protocols: [BUILTIN_PROVIDER_PROTOCOL.FRONTEND_SDK],\n publicConfig: {\n integrationKind: 'browser-error-monitoring',\n },\n csp: {\n derivedOrigins: [\n { publicConfigKey: 'dsn', bucket: ProviderFrontendCspOriginBucket.CONNECT },\n ],\n },\n sdk: {\n descriptor: { packageName: '@sentry/browser' },\n async activate({ providerRef, publicConfig }) {\n const dsn = publicConfig.dsn;\n if (typeof dsn !== 'string' || dsn.length === 0) {\n throw new Error(\n `Provider \"${providerRef}\" needs a Sentry DSN in its publicConfig.dsn. Without one the SDK starts `\n + 'and reports nothing, which is indistinguishable from a healthy application. Supply it by mapping '\n + \"this provider's contribution in the application's own provider-contributions.\",\n );\n }\n\n // DYNAMIC on purpose: `@sentry/browser` is a declared OPTIONAL peer of this\n // package, so it becomes its own chunk and only an application that turns\n // Sentry on pays for it.\n const Sentry = await import('@sentry/browser');\n const client = Sentry.init({ dsn });\n\n const sink: FrontendErrorMonitoringSink = {\n reportCrash(report: FrontendCrashReport): void {\n /*\n * Rebuilt as a real `Error` rather than passed as a plain object, because\n * that is the only shape from which Sentry derives a grouped ISSUE. Given a\n * plain object it records an unhelpful \"Non-Error exception captured\" with\n * no stack, so every crash in the application would collapse into one\n * issue — which is the same as having none.\n *\n * The stack is transplanted from the report: the error was constructed and\n * thrown somewhere else entirely, and a stack captured HERE would describe\n * this line, in the bridge, on every single crash.\n */\n const error = new Error(report.message);\n error.name = report.name;\n if (report.stack !== undefined) {\n error.stack = report.stack;\n }\n\n Sentry.captureException(error, {\n tags: report.tags,\n // React's component stack is not a JavaScript stack and must not be\n // merged into one. As `contexts` it renders as its own labelled block,\n // which is where someone reading the issue looks for \"which screen\".\n contexts:\n report.componentStack === undefined\n ? undefined\n : { react: { componentStack: report.componentStack } },\n });\n },\n };\n\n return {\n handle: sink,\n deactivate: async () => {\n await client?.close();\n },\n };\n },\n },\n /**\n * Same vendor, same research as the website module (2026-09-06): legal entity\n * `Functional Software, Inc.` from Sentry's own DPA, and regions given as the\n * vendor's OWN identifiers — the API subdomains `us` (Iowa, `us.sentry.io`) and\n * `de` (Frankfurt, `de.sentry.io`) — rather than mapped onto AWS-style labels,\n * which would be a jurisdiction determination the schema declines to model.\n *\n * Both deployment models, because self-hosted Sentry is a real product and the\n * region is then the operator's own.\n */\n complianceProfile: {\n deploymentModels: [ProviderDeploymentModel.SELF_HOSTED, ProviderDeploymentModel.VENDOR_HOSTED],\n processingRegions: ['us', 'de'],\n vendorLegalEntityName: 'Functional Software, Inc.',\n },\n};\n"]}
|
|
@@ -1,3 +1,30 @@
|
|
|
1
1
|
import type { FrontendWebsiteProviderModule } from '../../website/frontend-website-provider-module.types';
|
|
2
|
+
/**
|
|
3
|
+
* Sentry browser error monitoring for the marketing website.
|
|
4
|
+
*
|
|
5
|
+
* `FRONTEND_SDK` was a LABEL on this module until #332: the website resolved
|
|
6
|
+
* this provider's ref, stamped it into a `data-*` attribute on the page root,
|
|
7
|
+
* and loaded nothing. It now declares the package, loads it on demand and
|
|
8
|
+
* starts it.
|
|
9
|
+
*
|
|
10
|
+
* ## The DSN, and why the CSP origin is DERIVED rather than listed
|
|
11
|
+
*
|
|
12
|
+
* Sentry sends to the host inside the DSN, and a DSN is per APPLICATION and
|
|
13
|
+
* often per ENVIRONMENT — `https://<key>@o0.ingest.<region>.sentry.io/<id>`.
|
|
14
|
+
* No static list on this module can contain it. Listing a vendor's public
|
|
15
|
+
* ingest hostnames here instead would be a guess about someone else's
|
|
16
|
+
* infrastructure, wrong for every self-hosted Sentry, and wrong in production
|
|
17
|
+
* only.
|
|
18
|
+
*
|
|
19
|
+
* So the module declares WHERE the origin is rather than WHAT it is, and the
|
|
20
|
+
* CLI reads it out of the application's own `publicConfig.dsn` when it composes
|
|
21
|
+
* that service's policy. The application authors the DSN once, and the origin
|
|
22
|
+
* it implies cannot drift from it.
|
|
23
|
+
*
|
|
24
|
+
* The application supplies `dsn` by mapping this contribution in its own
|
|
25
|
+
* `provider-contributions.ts`; without one the SDK would start and collect
|
|
26
|
+
* nothing, so activation refuses instead — the runner isolates that failure and
|
|
27
|
+
* reports it, and no other provider is affected.
|
|
28
|
+
*/
|
|
2
29
|
export declare const SentryFrontendWebsiteProvider: FrontendWebsiteProviderModule;
|
|
3
30
|
//# sourceMappingURL=sentry.frontend-website.module.d.ts.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"sentry.frontend-website.module.d.ts","sourceRoot":"","sources":["../../../../../src/providers/sentry/sentry.frontend-website.module.ts"],"names":[],"mappings":"
|
|
1
|
+
{"version":3,"file":"sentry.frontend-website.module.d.ts","sourceRoot":"","sources":["../../../../../src/providers/sentry/sentry.frontend-website.module.ts"],"names":[],"mappings":"AAUA,OAAO,KAAK,EAAE,6BAA6B,EAAE,MAAM,sDAAsD,CAAC;AAE1G;;;;;;;;;;;;;;;;;;;;;;;;;;GA0BG;AACH,eAAO,MAAM,6BAA6B,EAAE,6BA8D3C,CAAC"}
|
|
@@ -1,14 +1,89 @@
|
|
|
1
|
-
import {
|
|
1
|
+
import { ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME } from '../../engine-frontend-providers-package.js';
|
|
2
|
+
import { ProviderDeploymentModel, BUILTIN_PROVIDER_CAPABILITY, BUILTIN_PROVIDER_PROTOCOL, ProviderFrontendCspOriginBucket, ProviderTier, defineProviderMetadata, ENGINE_PROVIDER_ORIGIN, } from '@wildo-ai/saas-models/public-runtime';
|
|
3
|
+
/**
|
|
4
|
+
* Sentry browser error monitoring for the marketing website.
|
|
5
|
+
*
|
|
6
|
+
* `FRONTEND_SDK` was a LABEL on this module until #332: the website resolved
|
|
7
|
+
* this provider's ref, stamped it into a `data-*` attribute on the page root,
|
|
8
|
+
* and loaded nothing. It now declares the package, loads it on demand and
|
|
9
|
+
* starts it.
|
|
10
|
+
*
|
|
11
|
+
* ## The DSN, and why the CSP origin is DERIVED rather than listed
|
|
12
|
+
*
|
|
13
|
+
* Sentry sends to the host inside the DSN, and a DSN is per APPLICATION and
|
|
14
|
+
* often per ENVIRONMENT — `https://<key>@o0.ingest.<region>.sentry.io/<id>`.
|
|
15
|
+
* No static list on this module can contain it. Listing a vendor's public
|
|
16
|
+
* ingest hostnames here instead would be a guess about someone else's
|
|
17
|
+
* infrastructure, wrong for every self-hosted Sentry, and wrong in production
|
|
18
|
+
* only.
|
|
19
|
+
*
|
|
20
|
+
* So the module declares WHERE the origin is rather than WHAT it is, and the
|
|
21
|
+
* CLI reads it out of the application's own `publicConfig.dsn` when it composes
|
|
22
|
+
* that service's policy. The application authors the DSN once, and the origin
|
|
23
|
+
* it implies cannot drift from it.
|
|
24
|
+
*
|
|
25
|
+
* The application supplies `dsn` by mapping this contribution in its own
|
|
26
|
+
* `provider-contributions.ts`; without one the SDK would start and collect
|
|
27
|
+
* nothing, so activation refuses instead — the runner isolates that failure and
|
|
28
|
+
* reports it, and no other provider is affected.
|
|
29
|
+
*/
|
|
2
30
|
export const SentryFrontendWebsiteProvider = {
|
|
3
|
-
metadata: {
|
|
31
|
+
metadata: defineProviderMetadata({
|
|
4
32
|
ref: 'sentry',
|
|
5
|
-
|
|
6
|
-
|
|
33
|
+
packageName: ENGINE_FRONTEND_PROVIDERS_PACKAGE_NAME,
|
|
34
|
+
tier: ProviderTier.MAIN,
|
|
35
|
+
origin: ENGINE_PROVIDER_ORIGIN,
|
|
36
|
+
}),
|
|
7
37
|
providerCapabilities: [BUILTIN_PROVIDER_CAPABILITY.FRONTEND_ERROR_MONITORING],
|
|
8
38
|
protocols: [BUILTIN_PROVIDER_PROTOCOL.FRONTEND_SDK],
|
|
9
39
|
publicConfig: {
|
|
10
40
|
integrationKind: 'browser-error-monitoring',
|
|
11
41
|
websiteRuntime: true,
|
|
12
42
|
},
|
|
43
|
+
csp: {
|
|
44
|
+
derivedOrigins: [
|
|
45
|
+
{ publicConfigKey: 'dsn', bucket: ProviderFrontendCspOriginBucket.CONNECT },
|
|
46
|
+
],
|
|
47
|
+
},
|
|
48
|
+
sdk: {
|
|
49
|
+
descriptor: { packageName: '@sentry/browser' },
|
|
50
|
+
async activate({ providerRef, publicConfig }) {
|
|
51
|
+
const dsn = publicConfig.dsn;
|
|
52
|
+
if (typeof dsn !== 'string' || dsn.length === 0) {
|
|
53
|
+
throw new Error(`Provider "${providerRef}" needs a Sentry DSN in its publicConfig.dsn. Without one the SDK starts `
|
|
54
|
+
+ 'and reports nothing, which is indistinguishable from a healthy site. Supply it by mapping this '
|
|
55
|
+
+ "provider's contribution in the application's own provider-contributions.");
|
|
56
|
+
}
|
|
57
|
+
// DYNAMIC on purpose: `@sentry/browser` is a declared OPTIONAL peer of
|
|
58
|
+
// this package, so it becomes its own chunk and only a surface that turns
|
|
59
|
+
// Sentry on pays for it. A static import would land it in every page that
|
|
60
|
+
// touches this closure and break outright wherever it is not installed.
|
|
61
|
+
const Sentry = await import('@sentry/browser');
|
|
62
|
+
const client = Sentry.init({ dsn });
|
|
63
|
+
return {
|
|
64
|
+
handle: client,
|
|
65
|
+
deactivate: async () => {
|
|
66
|
+
await client?.close();
|
|
67
|
+
},
|
|
68
|
+
};
|
|
69
|
+
},
|
|
70
|
+
},
|
|
71
|
+
/**
|
|
72
|
+
* Researched 2026-09-06; this vendor has NO backend counterpart to mirror.
|
|
73
|
+
*
|
|
74
|
+
* Legal entity from Sentry's own DPA — `Functional Software, Inc.` trading as Sentry. Regions are
|
|
75
|
+
* the vendor's OWN identifiers, which are the API subdomains rather than cloud labels: `us`
|
|
76
|
+
* (Iowa, `us.sentry.io`) and `de` (Frankfurt, `de.sentry.io`). Written that way deliberately —
|
|
77
|
+
* mapping a vendor's datacentre onto an AWS-style label is the jurisdiction determination the
|
|
78
|
+
* schema declines to model.
|
|
79
|
+
*
|
|
80
|
+
* The only frontend provider here declaring BOTH deployment models: self-hosted Sentry is a real
|
|
81
|
+
* product, so an operator can run it themselves and the region then becomes theirs.
|
|
82
|
+
*/
|
|
83
|
+
complianceProfile: {
|
|
84
|
+
deploymentModels: [ProviderDeploymentModel.SELF_HOSTED, ProviderDeploymentModel.VENDOR_HOSTED],
|
|
85
|
+
processingRegions: ['us', 'de'],
|
|
86
|
+
vendorLegalEntityName: 'Functional Software, Inc.',
|
|
87
|
+
},
|
|
13
88
|
};
|
|
14
89
|
//# sourceMappingURL=sentry.frontend-website.module.js.map
|