svelte-docinfo 0.5.4 → 0.6.0
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/README.md +69 -50
- package/dist/analyze-core.d.ts +179 -24
- package/dist/analyze-core.d.ts.map +1 -1
- package/dist/analyze-core.js +462 -42
- package/dist/analyze.d.ts +31 -6
- package/dist/analyze.d.ts.map +1 -1
- package/dist/analyze.js +29 -9
- package/dist/cli.d.ts +17 -7
- package/dist/cli.d.ts.map +1 -1
- package/dist/cli.js +12 -9
- package/dist/declaration-build.d.ts +14 -4
- package/dist/declaration-build.d.ts.map +1 -1
- package/dist/declaration-helpers.d.ts +65 -42
- package/dist/declaration-helpers.d.ts.map +1 -1
- package/dist/declaration-helpers.js +167 -72
- package/dist/dep-resolver.d.ts +38 -13
- package/dist/dep-resolver.d.ts.map +1 -1
- package/dist/dep-resolver.js +40 -22
- package/dist/diagnostics.d.ts +365 -14
- package/dist/diagnostics.d.ts.map +1 -1
- package/dist/diagnostics.js +112 -28
- package/dist/discovery.d.ts +7 -2
- package/dist/discovery.d.ts.map +1 -1
- package/dist/discovery.js +11 -5
- package/dist/exports.d.ts +39 -2
- package/dist/exports.d.ts.map +1 -1
- package/dist/exports.js +251 -46
- package/dist/files.d.ts +14 -2
- package/dist/files.d.ts.map +1 -1
- package/dist/files.js +49 -8
- package/dist/index.d.ts +9 -7
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +6 -4
- package/dist/logo.js +3 -3
- package/dist/paths.d.ts +22 -1
- package/dist/paths.d.ts.map +1 -1
- package/dist/paths.js +22 -1
- package/dist/postprocess.d.ts +31 -10
- package/dist/postprocess.d.ts.map +1 -1
- package/dist/postprocess.js +124 -76
- package/dist/session.d.ts +101 -11
- package/dist/session.d.ts.map +1 -1
- package/dist/session.js +457 -127
- package/dist/source-config.d.ts +210 -33
- package/dist/source-config.d.ts.map +1 -1
- package/dist/source-config.js +313 -26
- package/dist/source.d.ts +35 -0
- package/dist/source.d.ts.map +1 -1
- package/dist/source.js +37 -0
- package/dist/svelte.d.ts +81 -23
- package/dist/svelte.d.ts.map +1 -1
- package/dist/svelte.js +686 -359
- package/dist/tsdoc.d.ts +47 -12
- package/dist/tsdoc.d.ts.map +1 -1
- package/dist/tsdoc.js +70 -17
- package/dist/types.d.ts +967 -45
- package/dist/types.d.ts.map +1 -1
- package/dist/types.js +259 -48
- package/dist/typescript-alias-registry.d.ts +76 -0
- package/dist/typescript-alias-registry.d.ts.map +1 -0
- package/dist/typescript-alias-registry.js +206 -0
- package/dist/typescript-exports.d.ts +20 -15
- package/dist/typescript-exports.d.ts.map +1 -1
- package/dist/typescript-exports.js +264 -137
- package/dist/typescript-extract-class.d.ts +3 -4
- package/dist/typescript-extract-class.d.ts.map +1 -1
- package/dist/typescript-extract-class.js +71 -52
- package/dist/typescript-extract-function.d.ts +6 -8
- package/dist/typescript-extract-function.d.ts.map +1 -1
- package/dist/typescript-extract-function.js +20 -15
- package/dist/typescript-extract-shared.d.ts +309 -29
- package/dist/typescript-extract-shared.d.ts.map +1 -1
- package/dist/typescript-extract-shared.js +957 -127
- package/dist/typescript-extract-type-json.d.ts +286 -0
- package/dist/typescript-extract-type-json.d.ts.map +1 -0
- package/dist/typescript-extract-type-json.js +854 -0
- package/dist/typescript-extract-type-properties.d.ts +2 -3
- package/dist/typescript-extract-type-properties.d.ts.map +1 -1
- package/dist/typescript-extract-type-properties.js +91 -84
- package/dist/typescript-extract-type.d.ts +6 -8
- package/dist/typescript-extract-type.d.ts.map +1 -1
- package/dist/typescript-extract-type.js +138 -40
- package/dist/typescript-program.d.ts +106 -23
- package/dist/typescript-program.d.ts.map +1 -1
- package/dist/typescript-program.js +182 -54
- package/dist/vite.d.ts +23 -8
- package/dist/vite.d.ts.map +1 -1
- package/dist/vite.js +34 -14
- package/package.json +17 -15
- package/virtual-svelte-docinfo.d.ts +1 -1
package/dist/diagnostics.d.ts
CHANGED
|
@@ -51,9 +51,14 @@
|
|
|
51
51
|
* ## File Path Contract
|
|
52
52
|
*
|
|
53
53
|
* `Diagnostic.file` is always project-root-relative — no leading slash,
|
|
54
|
-
* no `./` prefix. `analyze` / `analyzeFromFiles`
|
|
55
|
-
*
|
|
56
|
-
*
|
|
54
|
+
* no `./` prefix. `analyze` / `analyzeFromFiles` and the session
|
|
55
|
+
* (`setFile`/`setFiles` at ingest, `query` at analysis) normalize paths from
|
|
56
|
+
* all sources (extraction, discovery, dependency resolution) before
|
|
57
|
+
* returning. Consumers that need an absolute path can rejoin with
|
|
58
|
+
* `projectRoot`.
|
|
59
|
+
*
|
|
60
|
+
* It names a *file*, not a module: `ModuleJson.path` is relative to
|
|
61
|
+
* `sourceRoot`, so `file` is not a lookup key into `modules`.
|
|
57
62
|
*
|
|
58
63
|
* @module
|
|
59
64
|
*/
|
|
@@ -77,6 +82,7 @@ export declare const DiagnosticKind: z.ZodEnum<{
|
|
|
77
82
|
signature_analysis_failed: "signature_analysis_failed";
|
|
78
83
|
class_member_failed: "class_member_failed";
|
|
79
84
|
svelte_prop_failed: "svelte_prop_failed";
|
|
85
|
+
legacy_props: "legacy_props";
|
|
80
86
|
module_skipped: "module_skipped";
|
|
81
87
|
module_unreadable: "module_unreadable";
|
|
82
88
|
import_parse_failed: "import_parse_failed";
|
|
@@ -87,6 +93,7 @@ export declare const DiagnosticKind: z.ZodEnum<{
|
|
|
87
93
|
duplicate_declaration: "duplicate_declaration";
|
|
88
94
|
transform_failed: "transform_failed";
|
|
89
95
|
resolver_failed: "resolver_failed";
|
|
96
|
+
alias_lost: "alias_lost";
|
|
90
97
|
}>;
|
|
91
98
|
export type DiagnosticKind = z.infer<typeof DiagnosticKind>;
|
|
92
99
|
/**
|
|
@@ -104,6 +111,21 @@ export declare const TypeExtractionDiagnostic: z.ZodObject<{
|
|
|
104
111
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
105
112
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
106
113
|
* project-relative form before they reach consumers.
|
|
114
|
+
*
|
|
115
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
116
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
117
|
+
* run before any session exists. Their `file` is already
|
|
118
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
119
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
120
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
121
|
+
* the Vite plugin both make it before merging.
|
|
122
|
+
*
|
|
123
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
124
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
125
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
126
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
127
|
+
* the same file under a second name. Absolute is what the pass can
|
|
128
|
+
* actually correct.
|
|
107
129
|
*/
|
|
108
130
|
file: z.ZodString;
|
|
109
131
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -134,6 +156,21 @@ export declare const SignatureAnalysisDiagnostic: z.ZodObject<{
|
|
|
134
156
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
135
157
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
136
158
|
* project-relative form before they reach consumers.
|
|
159
|
+
*
|
|
160
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
161
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
162
|
+
* run before any session exists. Their `file` is already
|
|
163
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
164
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
165
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
166
|
+
* the Vite plugin both make it before merging.
|
|
167
|
+
*
|
|
168
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
169
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
170
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
171
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
172
|
+
* the same file under a second name. Absolute is what the pass can
|
|
173
|
+
* actually correct.
|
|
137
174
|
*/
|
|
138
175
|
file: z.ZodString;
|
|
139
176
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -166,6 +203,21 @@ export declare const ClassMemberDiagnostic: z.ZodObject<{
|
|
|
166
203
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
167
204
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
168
205
|
* project-relative form before they reach consumers.
|
|
206
|
+
*
|
|
207
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
208
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
209
|
+
* run before any session exists. Their `file` is already
|
|
210
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
211
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
212
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
213
|
+
* the Vite plugin both make it before merging.
|
|
214
|
+
*
|
|
215
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
216
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
217
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
218
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
219
|
+
* the same file under a second name. Absolute is what the pass can
|
|
220
|
+
* actually correct.
|
|
169
221
|
*/
|
|
170
222
|
file: z.ZodString;
|
|
171
223
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -183,6 +235,13 @@ export declare const ClassMemberDiagnostic: z.ZodObject<{
|
|
|
183
235
|
export type ClassMemberDiagnostic = z.infer<typeof ClassMemberDiagnostic>;
|
|
184
236
|
/**
|
|
185
237
|
* Svelte prop type resolution failed.
|
|
238
|
+
*
|
|
239
|
+
* `file` is the original `.svelte` path, so `line`/`column` are present only
|
|
240
|
+
* when the prop's declaration lives in the component's own virtual *and* maps
|
|
241
|
+
* back to the original source — an imported props type or a node svelte2tsx
|
|
242
|
+
* synthesized leaves the position absent rather than publishing a virtual
|
|
243
|
+
* line, the rule `remapVirtualDiagnosticPositions` applies to extractor
|
|
244
|
+
* diagnostics.
|
|
186
245
|
*/
|
|
187
246
|
export declare const SveltePropDiagnostic: z.ZodObject<{
|
|
188
247
|
/** Name of the component. */
|
|
@@ -198,6 +257,21 @@ export declare const SveltePropDiagnostic: z.ZodObject<{
|
|
|
198
257
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
199
258
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
200
259
|
* project-relative form before they reach consumers.
|
|
260
|
+
*
|
|
261
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
262
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
263
|
+
* run before any session exists. Their `file` is already
|
|
264
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
265
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
266
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
267
|
+
* the Vite plugin both make it before merging.
|
|
268
|
+
*
|
|
269
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
270
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
271
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
272
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
273
|
+
* the same file under a second name. Absolute is what the pass can
|
|
274
|
+
* actually correct.
|
|
201
275
|
*/
|
|
202
276
|
file: z.ZodString;
|
|
203
277
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -213,6 +287,60 @@ export declare const SveltePropDiagnostic: z.ZodObject<{
|
|
|
213
287
|
kind: z.ZodLiteral<"svelte_prop_failed">;
|
|
214
288
|
}, z.core.$strict>;
|
|
215
289
|
export type SveltePropDiagnostic = z.infer<typeof SveltePropDiagnostic>;
|
|
290
|
+
/**
|
|
291
|
+
* Legacy (runes-less) component props detected — not extracted.
|
|
292
|
+
*
|
|
293
|
+
* `export let` components are still-legal Svelte 5 syntax, but prop extraction
|
|
294
|
+
* anchors on the `$props()` declaration, so their props yield no
|
|
295
|
+
* `ComponentPropJson` entries. Emitted once per component, listing the
|
|
296
|
+
* detected prop names — exported `let`/`var` statements plus export-clause
|
|
297
|
+
* renames of mutable bindings (`export {a as b}`) — with `line` pointing at
|
|
298
|
+
* the first legacy prop export in the original `.svelte` source.
|
|
299
|
+
*/
|
|
300
|
+
export declare const LegacyPropsDiagnostic: z.ZodObject<{
|
|
301
|
+
/** Name of the component. */
|
|
302
|
+
componentName: z.ZodString;
|
|
303
|
+
/** Exported prop names, in source order. */
|
|
304
|
+
propNames: z.ZodArray<z.ZodString>;
|
|
305
|
+
/**
|
|
306
|
+
* File path relative to project root (no leading slash, no `./` prefix).
|
|
307
|
+
*
|
|
308
|
+
* Normalized at every public API boundary — `session.setFile`/`setFiles`
|
|
309
|
+
* (ingest-time), `session.query` (query-time, via `analyzeCore`), and the
|
|
310
|
+
* one-shot wrappers `analyze` / `analyzeFromFiles`. Producers inside the
|
|
311
|
+
* pipeline may write absolute or virtual paths (e.g.,
|
|
312
|
+
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
313
|
+
* project-relative form before they reach consumers.
|
|
314
|
+
*
|
|
315
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
316
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
317
|
+
* run before any session exists. Their `file` is already
|
|
318
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
319
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
320
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
321
|
+
* the Vite plugin both make it before merging.
|
|
322
|
+
*
|
|
323
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
324
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
325
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
326
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
327
|
+
* the same file under a second name. Absolute is what the pass can
|
|
328
|
+
* actually correct.
|
|
329
|
+
*/
|
|
330
|
+
file: z.ZodString;
|
|
331
|
+
/** Line number (1-based), absent if location unavailable. */
|
|
332
|
+
line: z.ZodOptional<z.ZodNumber>;
|
|
333
|
+
/** Column number (1-based), absent if location unavailable. */
|
|
334
|
+
column: z.ZodOptional<z.ZodNumber>;
|
|
335
|
+
/** Human-readable description of the issue. */
|
|
336
|
+
message: z.ZodString;
|
|
337
|
+
severity: z.ZodEnum<{
|
|
338
|
+
error: "error";
|
|
339
|
+
warning: "warning";
|
|
340
|
+
}>;
|
|
341
|
+
kind: z.ZodLiteral<"legacy_props">;
|
|
342
|
+
}, z.core.$strict>;
|
|
343
|
+
export type LegacyPropsDiagnostic = z.infer<typeof LegacyPropsDiagnostic>;
|
|
216
344
|
/**
|
|
217
345
|
* Module was skipped during the analysis pass.
|
|
218
346
|
*
|
|
@@ -243,6 +371,21 @@ export declare const ModuleSkippedDiagnostic: z.ZodObject<{
|
|
|
243
371
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
244
372
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
245
373
|
* project-relative form before they reach consumers.
|
|
374
|
+
*
|
|
375
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
376
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
377
|
+
* run before any session exists. Their `file` is already
|
|
378
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
379
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
380
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
381
|
+
* the Vite plugin both make it before merging.
|
|
382
|
+
*
|
|
383
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
384
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
385
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
386
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
387
|
+
* the same file under a second name. Absolute is what the pass can
|
|
388
|
+
* actually correct.
|
|
246
389
|
*/
|
|
247
390
|
file: z.ZodString;
|
|
248
391
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -276,6 +419,21 @@ export declare const ModuleUnreadableDiagnostic: z.ZodObject<{
|
|
|
276
419
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
277
420
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
278
421
|
* project-relative form before they reach consumers.
|
|
422
|
+
*
|
|
423
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
424
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
425
|
+
* run before any session exists. Their `file` is already
|
|
426
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
427
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
428
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
429
|
+
* the Vite plugin both make it before merging.
|
|
430
|
+
*
|
|
431
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
432
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
433
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
434
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
435
|
+
* the same file under a second name. Absolute is what the pass can
|
|
436
|
+
* actually correct.
|
|
279
437
|
*/
|
|
280
438
|
file: z.ZodString;
|
|
281
439
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -304,6 +462,21 @@ export declare const ImportParseDiagnostic: z.ZodObject<{
|
|
|
304
462
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
305
463
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
306
464
|
* project-relative form before they reach consumers.
|
|
465
|
+
*
|
|
466
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
467
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
468
|
+
* run before any session exists. Their `file` is already
|
|
469
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
470
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
471
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
472
|
+
* the Vite plugin both make it before merging.
|
|
473
|
+
*
|
|
474
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
475
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
476
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
477
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
478
|
+
* the same file under a second name. Absolute is what the pass can
|
|
479
|
+
* actually correct.
|
|
307
480
|
*/
|
|
308
481
|
file: z.ZodString;
|
|
309
482
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -338,6 +511,21 @@ export declare const DuplicateCommentDiagnostic: z.ZodObject<{
|
|
|
338
511
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
339
512
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
340
513
|
* project-relative form before they reach consumers.
|
|
514
|
+
*
|
|
515
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
516
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
517
|
+
* run before any session exists. Their `file` is already
|
|
518
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
519
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
520
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
521
|
+
* the Vite plugin both make it before merging.
|
|
522
|
+
*
|
|
523
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
524
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
525
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
526
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
527
|
+
* the same file under a second name. Absolute is what the pass can
|
|
528
|
+
* actually correct.
|
|
341
529
|
*/
|
|
342
530
|
file: z.ZodString;
|
|
343
531
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -359,8 +547,9 @@ export type DuplicateCommentDiagnostic = z.infer<typeof DuplicateCommentDiagnost
|
|
|
359
547
|
* Two contexts emit this:
|
|
360
548
|
*
|
|
361
549
|
* - **Non-primary overload signature** — symbol-scope tags (`@example`,
|
|
362
|
-
* `@deprecated`, `@since`, `@see`, `@throws`, `@mutates`,
|
|
363
|
-
* `@nodocs`) describe the function as a whole, not individual
|
|
550
|
+
* `@deprecated`, `@internal`, `@since`, `@see`, `@throws`, `@mutates`,
|
|
551
|
+
* `@default`, `@nodocs`) describe the function as a whole, not individual
|
|
552
|
+
* signatures.
|
|
364
553
|
* The primary signature's JSDoc feeds the parent declaration's symbol-level
|
|
365
554
|
* extraction; tags on non-primary overload signatures are silently dropped
|
|
366
555
|
* from output. This diagnostic surfaces them so authors can move them to
|
|
@@ -376,17 +565,19 @@ export declare const MisplacedTagDiagnostic: z.ZodObject<{
|
|
|
376
565
|
/** The tag name without the `@` prefix (e.g., `'example'`, `'deprecated'`). */
|
|
377
566
|
tagName: z.ZodEnum<{
|
|
378
567
|
default: "default";
|
|
568
|
+
deprecated: "deprecated";
|
|
379
569
|
throws: "throws";
|
|
380
570
|
since: "since";
|
|
381
571
|
mutates: "mutates";
|
|
382
|
-
deprecated: "deprecated";
|
|
383
572
|
example: "example";
|
|
573
|
+
internal: "internal";
|
|
384
574
|
see: "see";
|
|
385
575
|
nodocs: "nodocs";
|
|
386
576
|
}>;
|
|
387
577
|
/**
|
|
388
|
-
* Name of the function or method whose overload
|
|
389
|
-
* Absent for module-comment misplacements (no
|
|
578
|
+
* Name of the enclosing symbol: the function or method whose overload
|
|
579
|
+
* carries the misplaced tag. Absent for module-comment misplacements (no
|
|
580
|
+
* enclosing symbol).
|
|
390
581
|
*/
|
|
391
582
|
functionName: z.ZodOptional<z.ZodString>;
|
|
392
583
|
/**
|
|
@@ -398,6 +589,21 @@ export declare const MisplacedTagDiagnostic: z.ZodObject<{
|
|
|
398
589
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
399
590
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
400
591
|
* project-relative form before they reach consumers.
|
|
592
|
+
*
|
|
593
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
594
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
595
|
+
* run before any session exists. Their `file` is already
|
|
596
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
597
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
598
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
599
|
+
* the Vite plugin both make it before merging.
|
|
600
|
+
*
|
|
601
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
602
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
603
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
604
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
605
|
+
* the same file under a second name. Absolute is what the pass can
|
|
606
|
+
* actually correct.
|
|
401
607
|
*/
|
|
402
608
|
file: z.ZodString;
|
|
403
609
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -433,6 +639,21 @@ export declare const UnknownParamDiagnostic: z.ZodObject<{
|
|
|
433
639
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
434
640
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
435
641
|
* project-relative form before they reach consumers.
|
|
642
|
+
*
|
|
643
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
644
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
645
|
+
* run before any session exists. Their `file` is already
|
|
646
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
647
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
648
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
649
|
+
* the Vite plugin both make it before merging.
|
|
650
|
+
*
|
|
651
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
652
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
653
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
654
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
655
|
+
* the same file under a second name. Absolute is what the pass can
|
|
656
|
+
* actually correct.
|
|
436
657
|
*/
|
|
437
658
|
file: z.ZodString;
|
|
438
659
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -460,7 +681,14 @@ export type UnknownParamDiagnostic = z.infer<typeof UnknownParamDiagnostic>;
|
|
|
460
681
|
export declare const DuplicateDeclarationDiagnostic: z.ZodObject<{
|
|
461
682
|
/** The duplicated declaration name. */
|
|
462
683
|
declarationName: z.ZodString;
|
|
463
|
-
/**
|
|
684
|
+
/**
|
|
685
|
+
* Module paths where the name was defined (>= 2).
|
|
686
|
+
*
|
|
687
|
+
* `ModuleJson.path` values — relative to `sourceRoot`, so a different base
|
|
688
|
+
* than the record's `file` (project-root-relative, like every diagnostic).
|
|
689
|
+
* The two disagree textually whenever `sourceRoot` is non-empty; each names
|
|
690
|
+
* what it says it names, a module vs. a file.
|
|
691
|
+
*/
|
|
464
692
|
modules: z.ZodArray<z.ZodString>;
|
|
465
693
|
/**
|
|
466
694
|
* File path relative to project root (no leading slash, no `./` prefix).
|
|
@@ -471,6 +699,21 @@ export declare const DuplicateDeclarationDiagnostic: z.ZodObject<{
|
|
|
471
699
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
472
700
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
473
701
|
* project-relative form before they reach consumers.
|
|
702
|
+
*
|
|
703
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
704
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
705
|
+
* run before any session exists. Their `file` is already
|
|
706
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
707
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
708
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
709
|
+
* the Vite plugin both make it before merging.
|
|
710
|
+
*
|
|
711
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
712
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
713
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
714
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
715
|
+
* the same file under a second name. Absolute is what the pass can
|
|
716
|
+
* actually correct.
|
|
474
717
|
*/
|
|
475
718
|
file: z.ZodString;
|
|
476
719
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -489,10 +732,12 @@ export type DuplicateDeclarationDiagnostic = z.infer<typeof DuplicateDeclaration
|
|
|
489
732
|
/**
|
|
490
733
|
* Source map parsing failed for a Svelte virtual file.
|
|
491
734
|
*
|
|
492
|
-
* Analysis continues
|
|
493
|
-
*
|
|
494
|
-
*
|
|
495
|
-
*
|
|
735
|
+
* Analysis continues without position mapping: query-time diagnostics drop
|
|
736
|
+
* `line`/`column` rather than point into svelte2tsx-generated TS — those
|
|
737
|
+
* emitted against the virtual via `remapVirtualDiagnosticPositions`,
|
|
738
|
+
* `svelte_prop_failed` at its own emission site — while declaration
|
|
739
|
+
* `sourceLine`s fall back to virtual positions. Rare; usually signals a
|
|
740
|
+
* malformed or incompatible svelte2tsx output.
|
|
496
741
|
*
|
|
497
742
|
* Emitted at ingest time by `transformSvelteSource` (in `svelte.ts`); flows
|
|
498
743
|
* through `setFile`/`setFiles` ingest diagnostics rather than the analysis
|
|
@@ -508,6 +753,21 @@ export declare const SourceMapFailedDiagnostic: z.ZodObject<{
|
|
|
508
753
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
509
754
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
510
755
|
* project-relative form before they reach consumers.
|
|
756
|
+
*
|
|
757
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
758
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
759
|
+
* run before any session exists. Their `file` is already
|
|
760
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
761
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
762
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
763
|
+
* the Vite plugin both make it before merging.
|
|
764
|
+
*
|
|
765
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
766
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
767
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
768
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
769
|
+
* the same file under a second name. Absolute is what the pass can
|
|
770
|
+
* actually correct.
|
|
511
771
|
*/
|
|
512
772
|
file: z.ZodString;
|
|
513
773
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -542,6 +802,21 @@ export declare const TransformFailedDiagnostic: z.ZodObject<{
|
|
|
542
802
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
543
803
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
544
804
|
* project-relative form before they reach consumers.
|
|
805
|
+
*
|
|
806
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
807
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
808
|
+
* run before any session exists. Their `file` is already
|
|
809
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
810
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
811
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
812
|
+
* the Vite plugin both make it before merging.
|
|
813
|
+
*
|
|
814
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
815
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
816
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
817
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
818
|
+
* the same file under a second name. Absolute is what the pass can
|
|
819
|
+
* actually correct.
|
|
545
820
|
*/
|
|
546
821
|
file: z.ZodString;
|
|
547
822
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -580,6 +855,21 @@ export declare const ResolverFailedDiagnostic: z.ZodObject<{
|
|
|
580
855
|
* pipeline may write absolute or virtual paths (e.g.,
|
|
581
856
|
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
582
857
|
* project-relative form before they reach consumers.
|
|
858
|
+
*
|
|
859
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
860
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
861
|
+
* run before any session exists. Their `file` is already
|
|
862
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
863
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
864
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
865
|
+
* the Vite plugin both make it before merging.
|
|
866
|
+
*
|
|
867
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
868
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
869
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
870
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
871
|
+
* the same file under a second name. Absolute is what the pass can
|
|
872
|
+
* actually correct.
|
|
583
873
|
*/
|
|
584
874
|
file: z.ZodString;
|
|
585
875
|
/** Line number (1-based), absent if location unavailable. */
|
|
@@ -595,6 +885,65 @@ export declare const ResolverFailedDiagnostic: z.ZodObject<{
|
|
|
595
885
|
kind: z.ZodLiteral<"resolver_failed">;
|
|
596
886
|
}, z.core.$strict>;
|
|
597
887
|
export type ResolverFailedDiagnostic = z.infer<typeof ResolverFailedDiagnostic>;
|
|
888
|
+
/**
|
|
889
|
+
* An exported type alias loses its name at use sites.
|
|
890
|
+
*
|
|
891
|
+
* The alias's right-hand side (an indexed access or conditional —
|
|
892
|
+
* `z.infer<typeof S>`, valibot's `InferOutput`) resolves to a pre-existing
|
|
893
|
+
* interned type that TypeScript never retroactively stamps an alias symbol
|
|
894
|
+
* on, so unannotated positions document the expansion instead of the name.
|
|
895
|
+
* Fires only where nothing self-heals: a loss the alias registry recovers
|
|
896
|
+
* (`typeInfo` emits `{kind: 'reference', name}` at use sites) is suppressed,
|
|
897
|
+
* as are literal-only unions (`z.enum` outputs) and brand-like intersections
|
|
898
|
+
* (`.brand()`) — readable degradations with no author-side fix worth
|
|
899
|
+
* demanding. `@nodocs` on the declaration suppresses. The author-side escape
|
|
900
|
+
* for a flagged alias is a nominal symbol, e.g.
|
|
901
|
+
* `interface Foo extends z.infer<typeof S> {}` where applicable.
|
|
902
|
+
*
|
|
903
|
+
* Always `warning`, query-time category (recomputed each `query()`).
|
|
904
|
+
*/
|
|
905
|
+
export declare const AliasLostDiagnostic: z.ZodObject<{
|
|
906
|
+
/** Name of the alias whose right-hand side resolves to a nameless type. */
|
|
907
|
+
aliasName: z.ZodString;
|
|
908
|
+
/**
|
|
909
|
+
* File path relative to project root (no leading slash, no `./` prefix).
|
|
910
|
+
*
|
|
911
|
+
* Normalized at every public API boundary — `session.setFile`/`setFiles`
|
|
912
|
+
* (ingest-time), `session.query` (query-time, via `analyzeCore`), and the
|
|
913
|
+
* one-shot wrappers `analyze` / `analyzeFromFiles`. Producers inside the
|
|
914
|
+
* pipeline may write absolute or virtual paths (e.g.,
|
|
915
|
+
* `Foo.svelte.__svelte2tsx__.ts`); normalization rewrites them to
|
|
916
|
+
* project-relative form before they reach consumers.
|
|
917
|
+
*
|
|
918
|
+
* The exception is **discovery** — `discoverSourceFiles` /
|
|
919
|
+
* `discoverFromExports` return their diagnostics unnormalized, since they
|
|
920
|
+
* run before any session exists. Their `file` is already
|
|
921
|
+
* project-root-relative, but `message` can embed an absolute path (an fs
|
|
922
|
+
* error names the file it failed on), so a consumer wiring discovery up
|
|
923
|
+
* itself owns the `normalizeDiagnosticPaths` call — `analyzeFromFiles` and
|
|
924
|
+
* the Vite plugin both make it before merging.
|
|
925
|
+
*
|
|
926
|
+
* **The absolute form is the one to write.** Normalization deliberately
|
|
927
|
+
* leaves an already-relative path alone (relativizing it would resolve
|
|
928
|
+
* against `cwd`), so a producer writing a `ModuleJson.path` — relative to
|
|
929
|
+
* `sourceRoot`, a different base — passes through untouched and publishes
|
|
930
|
+
* the same file under a second name. Absolute is what the pass can
|
|
931
|
+
* actually correct.
|
|
932
|
+
*/
|
|
933
|
+
file: z.ZodString;
|
|
934
|
+
/** Line number (1-based), absent if location unavailable. */
|
|
935
|
+
line: z.ZodOptional<z.ZodNumber>;
|
|
936
|
+
/** Column number (1-based), absent if location unavailable. */
|
|
937
|
+
column: z.ZodOptional<z.ZodNumber>;
|
|
938
|
+
/** Human-readable description of the issue. */
|
|
939
|
+
message: z.ZodString;
|
|
940
|
+
severity: z.ZodEnum<{
|
|
941
|
+
error: "error";
|
|
942
|
+
warning: "warning";
|
|
943
|
+
}>;
|
|
944
|
+
kind: z.ZodLiteral<"alias_lost">;
|
|
945
|
+
}, z.core.$strict>;
|
|
946
|
+
export type AliasLostDiagnostic = z.infer<typeof AliasLostDiagnostic>;
|
|
598
947
|
/**
|
|
599
948
|
* Discriminated union of all diagnostic variants.
|
|
600
949
|
*/
|
|
@@ -603,6 +952,7 @@ export declare const Diagnostic: z.ZodDiscriminatedUnion<[
|
|
|
603
952
|
typeof SignatureAnalysisDiagnostic,
|
|
604
953
|
typeof ClassMemberDiagnostic,
|
|
605
954
|
typeof SveltePropDiagnostic,
|
|
955
|
+
typeof LegacyPropsDiagnostic,
|
|
606
956
|
typeof ModuleSkippedDiagnostic,
|
|
607
957
|
typeof ModuleUnreadableDiagnostic,
|
|
608
958
|
typeof ImportParseDiagnostic,
|
|
@@ -612,7 +962,8 @@ export declare const Diagnostic: z.ZodDiscriminatedUnion<[
|
|
|
612
962
|
typeof SourceMapFailedDiagnostic,
|
|
613
963
|
typeof DuplicateDeclarationDiagnostic,
|
|
614
964
|
typeof TransformFailedDiagnostic,
|
|
615
|
-
typeof ResolverFailedDiagnostic
|
|
965
|
+
typeof ResolverFailedDiagnostic,
|
|
966
|
+
typeof AliasLostDiagnostic
|
|
616
967
|
], 'kind'>;
|
|
617
968
|
export type Diagnostic = z.infer<typeof Diagnostic>;
|
|
618
969
|
/**
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"diagnostics.d.ts","sourceRoot":"../src/lib/","sources":["../src/lib/diagnostics.ts"],"names":[],"mappings":"AAAA
|
|
1
|
+
{"version":3,"file":"diagnostics.d.ts","sourceRoot":"../src/lib/","sources":["../src/lib/diagnostics.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+DG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAIxB;;;;;GAKG;AACH,eAAO,MAAM,kBAAkB;;;EAA+B,CAAC;AAC/D,MAAM,MAAM,kBAAkB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,kBAAkB,CAAC,CAAC;AAIpE;;GAEG;AACH,eAAO,MAAM,cAAc;;;;;;;;;;;;;;;;;EAiBzB,CAAC;AACH,MAAM,MAAM,cAAc,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,cAAc,CAAC,CAAC;AAgD5D;;GAEG;AACH,eAAO,MAAM,wBAAwB;IAGpC,2DAA2D;;IAzC3D;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBAa9C,CAAC;AACH,MAAM,MAAM,wBAAwB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,wBAAwB,CAAC,CAAC;AAEhF;;GAEG;AACH,eAAO,MAAM,2BAA2B;IAGvC,sCAAsC;;IApDtC;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBAwB9C,CAAC;AACH,MAAM,MAAM,2BAA2B,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,2BAA2B,CAAC,CAAC;AAEtF;;GAEG;AACH,eAAO,MAAM,qBAAqB;IAGjC,yBAAyB;;IAEzB,sCAAsC;;IAjEtC;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBAqC9C,CAAC;AACH,MAAM,MAAM,qBAAqB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,qBAAqB,CAAC,CAAC;AAE1E;;;;;;;;;GASG;AACH,eAAO,MAAM,oBAAoB;IAGhC,6BAA6B;;IAE7B,wBAAwB;;IArFxB;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBAyD9C,CAAC;AACH,MAAM,MAAM,oBAAoB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,oBAAoB,CAAC,CAAC;AAExE;;;;;;;;;GASG;AACH,eAAO,MAAM,qBAAqB;IAGjC,6BAA6B;;IAE7B,4CAA4C;;IAzG5C;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBA6E9C,CAAC;AACH,MAAM,MAAM,qBAAqB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,qBAAqB,CAAC,CAAC;AAE1E;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,uBAAuB;IAGnC,qCAAqC;;;;;;IA/HrC;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBAmG9C,CAAC;AACH,MAAM,MAAM,uBAAuB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,uBAAuB,CAAC,CAAC;AAE9E;;;;;;;GAOG;AACH,eAAO,MAAM,0BAA0B;IA5ItC;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBAiH9C,CAAC;AACH,MAAM,MAAM,0BAA0B,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,0BAA0B,CAAC,CAAC;AAEpF;;GAEG;AACH,eAAO,MAAM,qBAAqB;IArJjC;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBA0H9C,CAAC;AACH,MAAM,MAAM,qBAAqB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,qBAAqB,CAAC,CAAC;AAE1E;;;GAGG;AACH,eAAO,MAAM,0BAA0B;IAGtC,wCAAwC;;;;;IAlKxC;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBAsI9C,CAAC;AACH,MAAM,MAAM,0BAA0B,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,0BAA0B,CAAC,CAAC;AAEpF;;;;;;;;;;;;;;;;;;;GAmBG;AACH,eAAO,MAAM,sBAAsB;IAGlC,+EAA+E;;;;;;;;;;;;IAY/E;;;;OAIG;;IA9MH;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBAkL9C,CAAC;AACH,MAAM,MAAM,sBAAsB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,sBAAsB,CAAC,CAAC;AAE5E;;;;;GAKG;AACH,eAAO,MAAM,sBAAsB;IAGlC,2DAA2D;;IAE3D,sCAAsC;;IA9NtC;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBAkM9C,CAAC;AACH,MAAM,MAAM,sBAAsB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,sBAAsB,CAAC,CAAC;AAE5E;;;;;;;;GAQG;AACH,eAAO,MAAM,8BAA8B;IAG1C,uCAAuC;;IAEvC;;;;;;;OAOG;;IAxPH;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBA4N9C,CAAC;AACH,MAAM,MAAM,8BAA8B,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,8BAA8B,CAAC,CAAC;AAE5F;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,yBAAyB;IA3QrC;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBAgP9C,CAAC;AACH,MAAM,MAAM,yBAAyB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,yBAAyB,CAAC,CAAC;AAElF;;;;;;;;GAQG;AACH,eAAO,MAAM,yBAAyB;IA1RrC;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBA+P9C,CAAC;AACH,MAAM,MAAM,yBAAyB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,yBAAyB,CAAC,CAAC;AAElF;;;;;;;;;;GAUG;AACH,eAAO,MAAM,wBAAwB;IAGpC,mDAAmD;;IA9SnD;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBAkR9C,CAAC;AACH,MAAM,MAAM,wBAAwB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,wBAAwB,CAAC,CAAC;AAEhF;;;;;;;;;;;;;;;;GAgBG;AACH,eAAO,MAAM,mBAAmB;IAG/B,2EAA2E;;IAvU3E;;;;;;;;;;;;;;;;;;;;;;;;OAwBG;;IAEH,6DAA6D;;IAE7D,+DAA+D;;IAE/D,+CAA+C;;;;;;;kBA2S9C,CAAC;AACH,MAAM,MAAM,mBAAmB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,mBAAmB,CAAC,CAAC;AAEtE;;GAEG;AACH,eAAO,MAAM,UAAU,EAAE,CAAC,CAAC,qBAAqB,CAC/C;IACC,OAAO,wBAAwB;IAC/B,OAAO,2BAA2B;IAClC,OAAO,qBAAqB;IAC5B,OAAO,oBAAoB;IAC3B,OAAO,qBAAqB;IAC5B,OAAO,uBAAuB;IAC9B,OAAO,0BAA0B;IACjC,OAAO,qBAAqB;IAC5B,OAAO,0BAA0B;IACjC,OAAO,sBAAsB;IAC7B,OAAO,sBAAsB;IAC7B,OAAO,yBAAyB;IAChC,OAAO,8BAA8B;IACrC,OAAO,yBAAyB;IAChC,OAAO,wBAAwB;IAC/B,OAAO,mBAAmB;CAC1B,EACD,MAAM,CAkBL,CAAC;AACH,MAAM,MAAM,UAAU,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,UAAU,CAAC,CAAC;AAIpD;;GAEG;AACH,eAAO,MAAM,SAAS,GAAI,aAAa,KAAK,CAAC,UAAU,CAAC,KAAG,OACX,CAAC;AAEjD;;GAEG;AACH,eAAO,MAAM,WAAW,GAAI,aAAa,KAAK,CAAC,UAAU,CAAC,KAAG,OACX,CAAC;AAEnD;;GAEG;AACH,eAAO,MAAM,QAAQ,GAAI,aAAa,KAAK,CAAC,UAAU,CAAC,KAAG,KAAK,CAAC,UAAU,CACxB,CAAC;AAEnD;;GAEG;AACH,eAAO,MAAM,UAAU,GAAI,aAAa,KAAK,CAAC,UAAU,CAAC,KAAG,KAAK,CAAC,UAAU,CACxB,CAAC;AAErD;;GAEG;AACH,eAAO,MAAM,MAAM,GAAI,CAAC,SAAS,cAAc,EAC9C,aAAa,KAAK,CAAC,UAAU,CAAC,EAC9B,MAAM,CAAC,KACL,KAAK,CAAC,OAAO,CAAC,UAAU,EAAE;IAAE,IAAI,EAAE,CAAC,CAAA;CAAE,CAAC,CAC6C,CAAC;AAEvF;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,gBAAgB,GAAI,YAAY,UAAU,KAAG,MAMzD,CAAC"}
|