strict-ts-lib-v5.1 0.5.0 → 0.6.0

package/CHANGELOG.md

@@ -0,0 +1,131 @@
+# strict-ts-lib-v5.1
+
+## 0.6.0
+
+### Minor Changes
+
+- ac290c1: Leave `Exclude`, `Extract`, `Omit` and `Pick` with the constraints TypeScript
+  declares, and widen `strict-ts-lib-v7.0`'s `typescript` peer range to
+  `>=6.0.0 <8.0.0`.
+
+    Both landed on main in #1672 and #1673 but shipped no release: those changesets
+    named the bundle packages (`strict-ts-lib-v7.0` and friends) rather than the
+    `-source` harnesses this repository versions. `changeset version` bumped the
+    bundle manifests, and `strict-lib:gen:packages` — which runs next and stamps
+    each bundle with its harness's version — wrote 0.5.1 straight back over them,
+    the harnesses never having been bumped at all. Nothing errored; the version
+    simply did not move.
+
+    All twelve harnesses are named. The `fixed` group in `.changeset/config.json`
+    would align the versions from a single name, but a changeset's text reaches
+    only the packages it names — the rest get a bare version heading with nothing
+    under it. A change to the shared converter affects every series equally, so
+    every series' changelog should say so.
+
+    ### `Exclude` and `Omit`
+
+    Two of the four utility types had their second argument narrowed here —
+    `Exclude<T, U extends T>` and `Omit<T, K extends keyof T>`, against upstream's
+    `Exclude<T, U>` and `Omit<T, K extends keyof any>`. `Extract` and `Pick`
+    already matched.
+
+    Narrowing makes a choice on the caller's behalf, and only one of the two
+    readings is ever right for a given call. Subtracting keys a type may not have
+    is legitimate — upstream's own declarations do it — and under the narrowed
+    constraint it is a TS2344 that nothing can fix when the declaration lives
+    inside a dependency. Making the choice explicit belongs in the caller's code,
+    which is what `eslint-plugin-ts-type-forge`'s
+    `prefer-strict-or-relaxed-utility-type` does, pointing at `StrictOmit` /
+    `RelaxedOmit` and the rest.
+
+    Only widens what is accepted, so anything that compiled still does.
+
+    ### Peer range
+
+    TypeScript 6.0.3 compiles the v7.0 lib set with `skipLibCheck: false` and no
+    errors, and resolves `@typescript/lib-*` by the same package-name lookup
+    TypeScript 7 uses, so one bundle serves both compilers. Without the wider
+    declaration npm refuses to install it beside TypeScript 6.
+
+## 0.5.1
+
+### Patch Changes
+
+- strict-ts-lib-scripts-common@0.0.1
+
+## 0.4.0
+
+### Minor Changes
+
+- 931dc7c: Ship every built-in library inside one package instead of ~107 per flavor: install one tarball and map @typescript/lib-* to its libs/ directory with tsconfig paths
+
+## 0.3.0
+
+### Minor Changes
+
+- 5ea9021: Stop `string & {}` from leaking into key types that are already `string`.
+
+    `Object.keys` and `Object.entries` open their key union with a `string & {}` arm
+    so that the declared keys still autocomplete while the excess keys a wider
+    object may carry are accepted. That arm only means something for a union of
+    string literals. Added to a key type that already contains `string` it produced
+    `string | (string & {})` — which _is_ `string`, just spelled in a way that then
+    showed up in everything computed from it.
+
+    The arm is now added only where it widens something (`WithOpenString`):
+
+    | expression                               | before                                                  | after                      |
+    | ---------------------------------------- | ------------------------------------------------------- | -------------------------- |
+    | `Object.keys(rec: Record<string, V>)`    | `(string \| (string & {}))[]`                           | `string[]`                 |
+    | `Object.entries(rec: Record<string, V>)` | `(readonly [string, V] \| readonly [string & {}, V])[]` | `(readonly [string, V])[]` |
+    | `Object.keys(obj: { a: 1; b: 2 })`       | `('a' \| 'b' \| (string & {}))[]`                       | unchanged                  |
+    | `Object.entries(obj: { a: 1; b: 2 })`    | keeps the open arm                                      | unchanged                  |
+
+    This also fixes `Object.fromEntries(Object.entries(rec).map(...))` on a record
+    keyed by an index signature. `PartialIfKeyIsUnion` wraps the result in `Partial`
+    when the key is a union, and the redundant arm made every key type a union — so
+    `Record<string, V>` came back as `Partial<Record<string | (string & {}), V>>`
+    and could not be assigned back to the record type it came from. With the arm
+    gone the key is plain `string`, which is not a union, so the result stays total.
+    Records with literal keys still get `Partial`, since entries genuinely may not
+    cover every declared key.
+
+    `PartialIfKeyIsUnion` itself is unchanged, as are hand-written entries arrays
+    and the fixed-length-tuple path.
+
+### Patch Changes
+
+- 9e98b83: Fix `Set` / `Map` subclassing, tighten the collection constructors, and publish three lib files at the subpath TypeScript actually looks up.
+
+    - `SetConstructor.prototype` / `MapConstructor.prototype` were narrowed to
+      `Set<never>` / `Map<never, never>`, which made every `class X extends Set<T>`
+      and `class X extends Map<K, V>` fail with TS2417 — `prototype` is what the
+      `extends` clause checks a subclass's static side against. They are now the
+      `ReadonlySet<unknown>` / `ReadonlyMap<unknown, unknown>` form, matching how
+      `ArrayConstructor.prototype` is already declared. The protection against an
+      untyped `new Set()` / `new Map()` swallowing anything is unchanged: it comes
+      from the constructor overloads, not from `prototype`.
+    - `lib.es2015.symbol.wellknown`, `lib.es2016.array.include` and
+      `lib.es2020.symbol.wellknown` were published one directory level too deep
+      (`es2015/symbol/wellknown` instead of `es2015/symbol-wellknown`), a subpath
+      `libReplacement` never resolves — so consumers silently got the stock
+      declarations for those three libs. They now land where TypeScript looks.
+    - An untyped `new WeakSet()` / `new WeakMap()` no longer accepts every object.
+      Both now default to `never`, like `new Set()` / `new Map()` already did.
+      `new WeakSet<object>()` and `new WeakMap<object, number>()` keep working,
+      because the no-argument overload carries its own type parameters.
+    - `null` is no longer an accepted initializer for any of the four collection
+      constructors. Upstream allows `new Set(null)` because the runtime tolerates
+      it, but a `null` reaching a collection constructor is a bug at the call site
+      rather than an intentional "start empty" — `new Set()` says that already.
+      Passing a plain optional still works (`(xs?: readonly T[]) => new Set(xs)`);
+      code that types its own parameter as `... | null` and forwards it has to drop
+      the `| null`. **This is the one change here that can require a consumer edit.**
+    - `Temporal.PartialTemporalLike` no longer trips this lib's narrowed
+      `Exclude<T, U extends T>` (TS2344).
+
+## 0.2.0
+
+### Minor Changes
+
+- c0c9f9d: Bump all packages (minor).

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -12,25 +12,30 @@ Every built-in library ships inside this one package, in two flavors:
 - `libs/` — plain `number`
 - `libs-branded/` — branded number types (`Uint8`, `SafeUint`, …)
 
-Pick one with `paths` in your `tsconfig.json`:
+TypeScript 5.1 resolves `@typescript/lib-*` as ordinary
+package names, through a fixed Node10 lookup — it does not read `paths`
+for this. Run the linker this package ships to supply those names. It
+creates one symlink per lib group under `node_modules/@typescript/`:
+
+```sh
+npx strict-ts-lib-v5.1-link             # plain `number`
+npx strict-ts-lib-v5.1-link --branded   # branded number types
+```
+
+Add it to your own `package.json` so that a reinstall restores the links:
 
 ```jsonc
 {
-    "compilerOptions": {
-        "libReplacement": true, // TypeScript 6.0 and later
-        "paths": {
-            "@typescript/lib-*": ["./node_modules/strict-ts-lib-v5.1/libs/*"],
-        },
+    "scripts": {
+        "prepare": "strict-ts-lib-v5.1-link",
     },
 }
 ```
 
-Two things to watch, because both fail silently — the replacement simply
-does not happen, with no error:
+Nothing goes in `tsconfig.json`: the lookup is unconditional at
+TypeScript 5.1, where `libReplacement` is not yet a known
+option — setting it is an error.
 
-- **`paths` is replaced, not merged, by a config that `extends` another**,
-  so it has to be written in whichever config TypeScript actually loads.
-- **The path is relative to the config that contains it**, which in a
-  monorepo package is usually `../../node_modules/…`.
+`--unlink` removes the links again.
 
-See <https://github.com/noshiro-pf/strict-typescript-lib> for usage and version support.
+See <https://github.com/noshiro-pf/mono> for usage and version support.

package/libs/dom/index.d.ts

@@ -33282,10 +33282,7 @@ interface MathMLElementTagNameMap {
 type ElementTagNameMap = HTMLElementTagNameMap &
   Pick<
     SVGElementTagNameMap,
-    import('ts-type-forge').RelaxedExclude<
-      keyof SVGElementTagNameMap,
-      keyof HTMLElementTagNameMap
-    >
+    Exclude<keyof SVGElementTagNameMap, keyof HTMLElementTagNameMap>
   >;
 
 declare const Audio: {

package/libs/es2017/object/index.d.ts

@@ -46,8 +46,7 @@ declare namespace StrictLibInternals {
                 ToStr<keyof PickByValue<R, R[K]>>,
                 R[K],
               ];
-              // eslint-disable-next-line @typescript-eslint/no-restricted-types
-            }[import('ts-type-forge').RelaxedExclude<keyof R, symbol>]
+            }[Exclude<keyof R, symbol>]
         )[]
       : never;
 }

package/libs/es5/index.d.ts

@@ -1859,7 +1859,7 @@ type Record<K extends PropertyKey, T> = {
 /**
  * Exclude from T those types that are assignable to U
  */
-type Exclude<T, U extends T> = T extends U ? never : T;
+type Exclude<T, U> = T extends U ? never : T;
 
 /**
  * Extract from T those types that are assignable to U
@@ -1869,7 +1869,7 @@ type Extract<T, U> = T extends U ? T : never;
 /**
  * Construct a type with the properties of T except for those in type K.
  */
-type Omit<T, K extends keyof T> = Pick<T, Exclude<keyof T, K>>;
+type Omit<T, K extends PropertyKey> = Pick<T, Exclude<keyof T, K>>;
 
 /**
  * Exclude null and undefined from T

package/libs-branded/dom/index.d.ts

@@ -33289,10 +33289,7 @@ interface MathMLElementTagNameMap {
 type ElementTagNameMap = HTMLElementTagNameMap &
   Pick<
     SVGElementTagNameMap,
-    import('ts-type-forge').RelaxedExclude<
-      keyof SVGElementTagNameMap,
-      keyof HTMLElementTagNameMap
-    >
+    Exclude<keyof SVGElementTagNameMap, keyof HTMLElementTagNameMap>
   >;
 
 declare const Audio: {

package/libs-branded/es2017/object/index.d.ts

@@ -46,8 +46,7 @@ declare namespace StrictLibInternals {
                 ToStr<keyof PickByValue<R, R[K]>>,
                 R[K],
               ];
-              // eslint-disable-next-line @typescript-eslint/no-restricted-types
-            }[import('ts-type-forge').RelaxedExclude<keyof R, symbol>]
+            }[Exclude<keyof R, symbol>]
         )[]
       : never;
 }

package/libs-branded/es5/index.d.ts

@@ -2014,7 +2014,7 @@ type Record<K extends PropertyKey, T> = {
 /**
  * Exclude from T those types that are assignable to U
  */
-type Exclude<T, U extends T> = T extends U ? never : T;
+type Exclude<T, U> = T extends U ? never : T;
 
 /**
  * Extract from T those types that are assignable to U
@@ -2024,7 +2024,7 @@ type Extract<T, U> = T extends U ? T : never;
 /**
  * Construct a type with the properties of T except for those in type K.
  */
-type Omit<T, K extends keyof T> = Pick<T, Exclude<keyof T, K>>;
+type Omit<T, K extends PropertyKey> = Pick<T, Exclude<keyof T, K>>;
 
 /**
  * Exclude null and undefined from T

package/link-libs.mjs

@@ -0,0 +1,206 @@
+#!/usr/bin/env node
+// Copied verbatim into every published bundle by `gen-packages.mts`, and run
+// by consumers as `npx <package>-link`. Plain JavaScript with no dependencies,
+// because it runs from inside `node_modules` in someone else's project.
+//
+// WHAT IT IS FOR
+//
+// TypeScript resolves a lib replacement in one of two ways, and which one
+// depends on the version — they are exclusive, both measured:
+//
+//   - TypeScript 7 reads `paths`, and no longer looks `@typescript/lib-*` up
+//     by name. Those consumers need no linking; the README's `paths` entry is
+//     the whole setup.
+//   - TypeScript 6 and earlier ignore `paths` here and resolve
+//     `@typescript/lib-<group>` as an ordinary package name, through a fixed
+//     Node10 lookup. A single package shipping every lib as a subdirectory has
+//     no name for them to find.
+//
+// This script supplies those names: one symlink per lib group, from
+// `node_modules/@typescript/lib-<group>` to this package's `libs/<group>`.
+// A directory holding an `index.d.ts` resolves without a manifest of its own,
+// so nothing else has to ship.
+//
+// USAGE
+//
+//   npx <package>-link                 link the plain-number flavor
+//   npx <package>-link --branded       link the branded flavor
+//   npx <package>-link --dir <path>    treat <path> as the project root
+//   npx <package>-link --unlink        remove the links again
+//
+// Add it to your own `package.json` so a reinstall restores the links:
+//
+//   { "scripts": { "prepare": "<package>-link" } }
+
+import * as fs from 'node:fs/promises';
+import * as path from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const SCOPE = '@typescript';
+
+const main = async () => {
+  const options = parseArgs(process.argv.slice(2));
+
+  const packageDir = path.dirname(fileURLToPath(import.meta.url));
+
+  const packageName = await readPackageName(packageDir);
+
+  const flavor = options.branded ? 'libs-branded' : 'libs';
+
+  const libsDir = path.join(packageDir, flavor);
+
+  const groups = await readGroups(libsDir);
+
+  if (groups.length === 0) {
+    throw new Error(`No lib groups found in ${libsDir}.`);
+  }
+
+  const scopeDir = path.join(
+    await resolveNodeModules(options.dir, packageDir, packageName),
+    SCOPE,
+  );
+
+  await fs.mkdir(scopeDir, { recursive: true });
+
+  for (const group of groups) {
+    const linkPath = path.join(scopeDir, `lib-${group}`);
+
+    await removeIfPresent(linkPath);
+
+    if (options.unlink) continue;
+
+    // Relative on POSIX so the tree stays portable; a Windows junction is
+    // the only kind of directory link an unprivileged user can make, and it
+    // takes an absolute target.
+    const target =
+      process.platform === 'win32'
+        ? path.join(packageDir, flavor, group)
+        : path.join('..', packageName, flavor, group);
+
+    await fs.symlink(
+      target,
+      linkPath,
+      process.platform === 'win32' ? 'junction' : 'dir',
+    );
+
+    // A dangling link is the one failure mode that would look like success:
+    // TypeScript falls back to its own declarations without saying anything.
+    if (!(await exists(linkPath))) {
+      throw new Error(
+        `${linkPath} -> ${target} does not resolve. Is ${packageName} installed in this project?`,
+      );
+    }
+  }
+
+  console.info(
+    options.unlink
+      ? `Removed ${groups.length} ${SCOPE}/lib-* links from ${scopeDir}.`
+      : `Linked ${groups.length} ${SCOPE}/lib-* to ${packageName}/${flavor} in ${scopeDir}.`,
+  );
+};
+
+const parseArgs = (argv) => {
+  const dirIndex = argv.indexOf('--dir');
+
+  return {
+    branded: argv.includes('--branded'),
+    unlink: argv.includes('--unlink'),
+    dir: dirIndex === -1 ? undefined : argv[dirIndex + 1],
+  };
+};
+
+/**
+ * The `node_modules` to link into: the one this package was installed in.
+ *
+ * Not "the nearest `node_modules` above the working directory" — in a
+ * monorepo that finds the workspace root, and the links land next to a copy
+ * of this package that is not there, which the caller then has to notice.
+ * The anchor is the package itself:
+ *
+ * 1. `--dir` wins outright.
+ * 2. If this file sits directly under a `node_modules`, that is the answer.
+ *    npm and yarn install that way.
+ * 3. pnpm does not — the real path is inside `.pnpm`, reached through a
+ *    symlink — so walk up from the working directory for the first project
+ *    whose `node_modules` holds this package by name.
+ */
+const resolveNodeModules = async (explicitDir, packageDir, packageName) => {
+  if (explicitDir !== undefined) {
+    return path.resolve(explicitDir, 'node_modules');
+  }
+
+  const parent = path.dirname(packageDir);
+
+  if (
+    path.basename(parent) === 'node_modules' &&
+    !parent.split(path.sep).includes('.pnpm')
+  ) {
+    return parent;
+  }
+
+  let mut_dir = process.cwd();
+
+  for (;;) {
+    const candidate = path.join(mut_dir, 'node_modules');
+
+    if (await exists(path.join(candidate, packageName))) return candidate;
+
+    const next = path.dirname(mut_dir);
+
+    if (next === mut_dir) {
+      throw new Error(
+        `Could not find a project with ${packageName} installed, starting from ${process.cwd()}. Run this from that project, or pass --dir <path>.`,
+      );
+    }
+
+    mut_dir = next;
+  }
+};
+
+const readGroups = async (libsDir) => {
+  const entries = await fs.readdir(libsDir, { withFileTypes: true });
+
+  return entries
+    .filter((entry) => entry.isDirectory())
+    .map((entry) => entry.name)
+    .sort();
+};
+
+const readPackageName = async (packageDir) => {
+  const raw = await fs.readFile(path.join(packageDir, 'package.json'), 'utf8');
+
+  const name = JSON.parse(raw).name;
+
+  if (typeof name !== 'string') {
+    throw new Error(`No name in ${packageDir}/package.json.`);
+  }
+
+  return name;
+};
+
+/**
+ * Only a symlink is removed. A real directory at `@typescript/lib-<group>` is
+ * someone else's package, and silently deleting it would be worse than
+ * failing.
+ */
+const removeIfPresent = async (linkPath) => {
+  const stats = await fs.lstat(linkPath).catch(() => undefined);
+
+  if (stats === undefined) return;
+
+  if (!stats.isSymbolicLink()) {
+    throw new Error(
+      `${linkPath} exists and is not a symlink; refusing to replace it.`,
+    );
+  }
+
+  await fs.unlink(linkPath);
+};
+
+const exists = async (target) =>
+  await fs.access(target).then(
+    () => true,
+    () => false,
+  );
+
+await main();

package/package.json

@@ -1,18 +1,23 @@
 {
   "name": "strict-ts-lib-v5.1",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "private": false,
   "description": "Strict TypeScript 5.1.6 standard library (all libs in one package)",
   "license": "Apache-2.0",
   "author": "noshiro-pf <noshiro.pf@gmail.com>",
   "repository": {
     "type": "git",
-    "url": "https://github.com/noshiro-pf/strict-typescript-lib.git"
+    "url": "https://github.com/noshiro-pf/mono.git"
+  },
+  "bin": {
+    "strict-ts-lib-v5.1-link": "./link-libs.mjs"
   },
   "files": [
     "libs",
     "libs-branded",
-    "!libs/**/package.json"
+    "!libs/**/package.json",
+    "link-libs.mjs",
+    "CHANGELOG.md"
   ],
   "type": "module",
   "sideEffects": false,
@@ -22,4 +27,4 @@
   "peerDependencies": {
     "typescript": ">=5.1.0 <5.2.0"
   }
-}
+}