@williamthorsen/tsconfig 0.1.1 → 0.2.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/README.md +2 -10
- package/package.json +1 -1
- package/tsconfig.base.json +1 -1
package/README.md
CHANGED
|
@@ -2,15 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Shared TypeScript base config for Node-only projects. Inlines the settings of [`@tsconfig/strictest`](https://www.npmjs.com/package/@tsconfig/strictest) and adds the Node and build options it leaves out, so a consuming repo declares only what is genuinely its own.
|
|
4
4
|
|
|
5
|
-
<!-- section:release-notes -->
|
|
6
|
-
## Release notes — v0.1.1 (2026-08-01)
|
|
7
|
-
|
|
8
|
-
### 🐛 Bug fixes
|
|
9
|
-
|
|
10
|
-
- Inline @tsconfig/strictest instead of extending it (#129)
|
|
11
|
-
|
|
12
|
-
Fixes an issue where, under pnpm, tools that resolve tsconfig files without following symlinks failed to find `@tsconfig/strictest`, breaking lint runs and builds in projects that declare only `@williamthorsen/tsconfig`. Consuming projects no longer need to add `@tsconfig/strictest` to their own `package.json` as a workaround.
|
|
13
|
-
<!-- /section:release-notes -->
|
|
5
|
+
<!-- section:release-notes --><!-- /section:release-notes -->
|
|
14
6
|
|
|
15
7
|
## Installation
|
|
16
8
|
|
|
@@ -48,7 +40,7 @@ Everything `@tsconfig/strictest` sets, plus the Node and build options it omits:
|
|
|
48
40
|
|
|
49
41
|
## What the consumer owns
|
|
50
42
|
|
|
51
|
-
The base
|
|
43
|
+
The base declares none of these:
|
|
52
44
|
|
|
53
45
|
- **`types`** — the ambient type packages in scope. Most Node projects want `["node"]`; declaring it narrows the default, which would otherwise pull in every `@types/*` package installed.
|
|
54
46
|
- **`paths`** — TypeScript resolves `baseUrl`-less `paths` relative to the file that _declares_ them, so a path alias set in this package would resolve inside `node_modules`. Aliases must be declared by the config that owns the source tree.
|
package/package.json
CHANGED
package/tsconfig.base.json
CHANGED
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
"compilerOptions": {
|
|
9
9
|
// Inlined from `@tsconfig/strictest`, in upstream's order. Not reached through `extends`, because
|
|
10
10
|
// resolvers that don't realpath pnpm symlinks can't follow the second hop. The root test
|
|
11
|
-
// `__tests__/tsconfig-base.
|
|
11
|
+
// `__tests__/tsconfig-base.tool.test.ts` asserts this block still matches the installed devDependency.
|
|
12
12
|
"strict": true,
|
|
13
13
|
"allowUnusedLabels": false,
|
|
14
14
|
"allowUnreachableCode": false,
|