| 10 | } |
| 11 | |
| 12 | export interface SourceMapOptions { |
| 13 | /** |
| 14 | * Whether the mapping should be high-resolution: |
| 15 | * - `false` (default) - lo-res mappings. Only one mapping per line, plus any locations added |
| 16 | * with `s.addSourcemapLocation()`. Quicker to generate and less bulky, but devtools may only |
| 17 | * be able to identify the correct line, not the exact column. |
| 18 | * - `true` - hi-res mappings. Every single character gets a mapping, so devtools can always |
| 19 | * pinpoint the exact location of function calls and so on. |
| 20 | * - `"boundary"` - semi-hi-res mappings, segmented per word boundary instead of per character. |
| 21 | * Suitable for string semantics that are separated by words. |
| 22 | * - `"experimental-range"` - hi-res mappings that use range mappings |
| 23 | * (https://github.com/tc39/ecma426/blob/main/proposals/range-mappings.md), a source map |
| 24 | * extension that can map all positions in a range with fewer mappings than mapping every |
| 25 | * character individually. This requires support for range mappings in the source map |
| 26 | * consumer, and the feature is experimental. |
| 27 | * |
| 28 | * If sourcemap locations have been specified with s.addSourceMapLocation(), they will be used here. |
| 29 | */ |
| 30 | hires?: boolean | 'boundary' | 'experimental-range' |
| 31 | /** |
| 32 | * The filename where you plan to write the sourcemap. |
| 33 | */ |
| 34 | file?: string |
| 35 | /** |
| 36 | * The filename of the file containing the original source. |
| 37 | */ |
| 38 | source?: string |
| 39 | /** |
| 40 | * Whether to include the original content in the map's sourcesContent array. |
| 41 | */ |
| 42 | includeContent?: boolean |
| 43 | } |
| 44 | |
| 45 | export type SourceMapSegment |
| 46 | = | [number] |
nothing calls this directly
no outgoing calls
no test coverage detected