@uniflowed/config 0.0.0-alpha.39 → 0.0.0-alpha.40
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/internal/schema.js +12 -0
- package/package.json +1 -1
package/internal/schema.js
CHANGED
|
@@ -625,6 +625,18 @@ export type UniflowedConfig = {
|
|
|
625
625
|
// `peerDependencies`, `optionalDependencies` and the host's built-in
|
|
626
626
|
// modules; this is for what a manifest cannot say.
|
|
627
627
|
readonly external?: $ReadOnlyArray<string>,
|
|
628
|
+
/**
|
|
629
|
+
* Write a TypeScript declaration file beside each entry. On by
|
|
630
|
+
* default.
|
|
631
|
+
*
|
|
632
|
+
* Most people who install a Flow library write TypeScript, and to them
|
|
633
|
+
* a package with no `.d.ts` is `any`. Every Flow construct that has no
|
|
634
|
+
* TypeScript meaning is named in the build report rather than silently
|
|
635
|
+
* widened, so turning this off is for a library that would rather ship
|
|
636
|
+
* no declarations than ones with gaps in them — not for one that wants
|
|
637
|
+
* to stop hearing about the gaps.
|
|
638
|
+
*/
|
|
639
|
+
readonly declarations?: boolean,
|
|
628
640
|
},
|
|
629
641
|
/**
|
|
630
642
|
* What `uf dev`, `uf build` and `uf preview` run on, when it is not the
|