|
| 1 | +export type SourceMapsOptions = { |
| 2 | + /** |
| 3 | + * If this flag is `true`, and an auth token is detected, the Sentry SDK will |
| 4 | + * automatically generate and upload source maps to Sentry during a production build. |
| 5 | + * |
| 6 | + * @default true |
| 7 | + */ |
| 8 | + enabled?: boolean; |
| 9 | + |
| 10 | + /** |
| 11 | + * The auth token to use when uploading source maps to Sentry. |
| 12 | + * |
| 13 | + * Instead of specifying this option, you can also set the `SENTRY_AUTH_TOKEN` environment variable. |
| 14 | + * |
| 15 | + * To create an auth token, follow this guide: |
| 16 | + * @see https://docs.sentry.io/product/accounts/auth-tokens/#organization-auth-tokens |
| 17 | + */ |
| 18 | + authToken?: string; |
| 19 | + |
| 20 | + /** |
| 21 | + * The organization slug of your Sentry organization. |
| 22 | + * Instead of specifying this option, you can also set the `SENTRY_ORG` environment variable. |
| 23 | + */ |
| 24 | + org?: string; |
| 25 | + |
| 26 | + /** |
| 27 | + * The project slug of your Sentry project. |
| 28 | + * Instead of specifying this option, you can also set the `SENTRY_PROJECT` environment variable. |
| 29 | + */ |
| 30 | + project?: string; |
| 31 | + |
| 32 | + /** |
| 33 | + * If this flag is `true`, the Sentry plugin will collect some telemetry data and send it to Sentry. |
| 34 | + * It will not collect any sensitive or user-specific data. |
| 35 | + * |
| 36 | + * @default true |
| 37 | + */ |
| 38 | + telemetry?: boolean; |
| 39 | + |
| 40 | + /** |
| 41 | + * Options related to sourcemaps |
| 42 | + */ |
| 43 | + sourcemaps?: { |
| 44 | + /** |
| 45 | + * A glob or an array of globs that specify the build artifacts and source maps that will be uploaded to Sentry. |
| 46 | + * |
| 47 | + * The globbing patterns must follow the implementation of the `glob` package. |
| 48 | + * @see https://www.npmjs.com/package/glob#glob-primer |
| 49 | + */ |
| 50 | + assets?: string | Array<string>; |
| 51 | + |
| 52 | + /** |
| 53 | + * A glob or an array of globs that specifies which build artifacts should not be uploaded to Sentry. |
| 54 | + * |
| 55 | + * @default [] - By default no files are ignored. Thus, all files matching the `assets` glob |
| 56 | + * or the default value for `assets` are uploaded. |
| 57 | + * |
| 58 | + * The globbing patterns follow the implementation of the glob package. (https://www.npmjs.com/package/glob) |
| 59 | + */ |
| 60 | + ignore?: string | Array<string>; |
| 61 | + |
| 62 | + /** |
| 63 | + * A glob or an array of globs that specifies the build artifacts that should be deleted after the artifact |
| 64 | + * upload to Sentry has been completed. |
| 65 | + * |
| 66 | + * @default [] - By default no files are deleted. |
| 67 | + * |
| 68 | + * The globbing patterns follow the implementation of the glob package. (https://www.npmjs.com/package/glob) |
| 69 | + */ |
| 70 | + filesToDeleteAfterUpload?: string | Array<string>; |
| 71 | + }; |
| 72 | + |
| 73 | + /** |
| 74 | + * Enable debug functionality of the SDK during build-time. |
| 75 | + * Enabling this will give you logs about source maps. |
| 76 | + */ |
| 77 | + debug?: boolean; |
| 78 | +}; |
| 79 | + |
| 80 | +/** |
| 81 | + * Build options for the Sentry module. These options are used during build-time by the Sentry SDK. |
| 82 | + */ |
| 83 | +export type SentrySolidStartPluginOptions = { |
| 84 | + /** |
| 85 | + * Options for the Sentry Vite plugin to customize the source maps upload process. |
| 86 | + */ |
| 87 | + sourceMapsUploadOptions?: SourceMapsOptions; |
| 88 | + |
| 89 | + /** |
| 90 | + * Enable debug functionality of the SDK during build-time. |
| 91 | + * Enabling this will give you, for example logs about source maps. |
| 92 | + */ |
| 93 | + debug?: boolean; |
| 94 | +}; |
0 commit comments