@jterrazz/typescript 9.1.0 → 9.1.1
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/package.json +1 -1
- package/presets/knip/base.json +22 -1
package/package.json
CHANGED
package/presets/knip/base.json
CHANGED
|
@@ -1,5 +1,26 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "https://unpkg.com/knip@6/schema.json",
|
|
3
3
|
"ignoreDependencies": ["@jterrazz/test", "@jterrazz/typescript"],
|
|
4
|
-
"ignoreBinaries": ["oxlint", "oxfmt"]
|
|
4
|
+
"ignoreBinaries": ["oxlint", "oxfmt"],
|
|
5
|
+
// Knip's own oxlint/oxfmt/vitest/tsdown plugins auto-enable only when
|
|
6
|
+
// that PACKAGE is a direct dependency of the project (`hasDependency`
|
|
7
|
+
// reads package.json). A consumer of this preset declares only
|
|
8
|
+
// `@jterrazz/typescript`, so those tools are never direct dependencies
|
|
9
|
+
// of its own — the plugins stay off and their config files read as
|
|
10
|
+
// unused. Naming the toolchain's own config files here, by hand, is
|
|
11
|
+
// the fix: an explicit `entry` always wins, regardless of the plugin.
|
|
12
|
+
//
|
|
13
|
+
// Setting `entry` at all REPLACES knip's own default (it does not add
|
|
14
|
+
// to it) — so the first two patterns below are knip's own defaults,
|
|
15
|
+
// repeated here on purpose, or a consumer with a bare `index.ts` and no
|
|
16
|
+
// `entry` of its own would lose it the moment this preset's `entry`
|
|
17
|
+
// took over.
|
|
18
|
+
"entry": [
|
|
19
|
+
"{index,cli,main}.{js,mjs,cjs,jsx,ts,tsx,mts,cts}!",
|
|
20
|
+
"src/{index,cli,main}.{js,mjs,cjs,jsx,ts,tsx,mts,cts}!",
|
|
21
|
+
"oxlint.config.ts",
|
|
22
|
+
"oxfmt.config.ts",
|
|
23
|
+
"vitest.config.{js,mjs,ts,cjs,mts,cts}",
|
|
24
|
+
"tsdown.config.{ts,mts,cts,js,mjs,cjs}"
|
|
25
|
+
]
|
|
5
26
|
}
|