From cfc944a10be35c03f6dfba32a133a4a71aa179ca Mon Sep 17 00:00:00 2001 From: Luca Forstner Date: Thu, 23 May 2024 13:07:40 +0200 Subject: [PATCH] docs: Clarify interaction between `uploadLegacySourcemaps` and other options --- packages/dev-utils/src/generate-documentation-table.ts | 2 ++ 1 file changed, 2 insertions(+) diff --git a/packages/dev-utils/src/generate-documentation-table.ts b/packages/dev-utils/src/generate-documentation-table.ts index 56cff549..1c9bbf63 100644 --- a/packages/dev-utils/src/generate-documentation-table.ts +++ b/packages/dev-utils/src/generate-documentation-table.ts @@ -245,6 +245,8 @@ Each path can be given as a string or an object with more specific options. The modern version of doing source maps upload is more robust and way easier to get working but has to inject a very small snippet of JavaScript into your output bundles. In situations where this leads to problems (e.g subresource integrity) you can use this option as a fallback. +Please note that this option will not interact with any settings provided in the \`sourcemaps\` option. Using \`uploadLegacySourcemaps\` is a completely separate upload mechanism we provide for backwards-compatibility. + The \`IncludeEntry\` type looks as follows: \`\`\`ts