doc(correct-ts-specifiers): put usage examples first in readme (#78)

Author: JakobJingleheimer

recipes/correct-ts-specifiers/README.md

@@ -4,56 +4,6 @@ This package transforms import specifiers from the old `tsc` (TypeScript's compi
 
 This is a one-and-done process, and the updated source-code should be committed to your version control (eg git); thereafter, source-code import statements should be authored compliant with the ECMAScript (JavaScript) standard.
 
-> [!TIP]
-> Those using `tsc` to compile will need to enable [`rewriteRelativeImportExtensions`](https://www.typescriptlang.org/tsconfig/#rewriteRelativeImportExtensions); using `tsc` for only type-checking (ex via a lint/test step like `npm run test:types`) needs [`allowImportingTsExtensions`](https://www.typescriptlang.org/tsconfig/#allowImportingTsExtensions) (and some additional compile options—see the cited documentation);
-
-This package does not just blindly find & replace file extensions within specifiers: It confirms that the replacement specifier actually exists; in ambiguous cases (such as two files with the same basename in the same location but different relevant file extensions like `/tmp/foo.js` and `/tmp/foo.ts`), it logs an error, skips that specifier, and continues processing.
-
-> [!CAUTION]
-> This package does not confirm that imported modules contain the desired export(s). This _shouldn't_ actually ever result in a problem because ambiguous cases are skipped (so if there is a problem, it existed before the migration started). Merely running your source-code after the mirgration completes will confirm all is well (if there are problems, node will error, citing the problems).
-
-> [!TIP]
-> Node.js requires the `type` keyword be present on type imports. For own code, this package usually handles that. However, in some cases and for node modules, it does not. Robust tooling already exists that will automatically fix this, such as
->
-> * [`use-import-type` via biome](https://biomejs.dev/linter/rules/use-import-type/)
-> * [`typescript/no-import-type-side-effects` via oxlint](https://oxc.rs/docs/guide/usage/linter/rules/typescript/no-import-type-side-effects)
-> * [`consistent-type-imports` via typescript-lint](https://typescript-eslint.io/rules/consistent-type-imports)
->
-> If your source code needs that, first run this codemod and then one of those fixers.
-
-## Running
-
-> [!CAUTION]
-> This will change your source-code. Commit any unsaved changes before running this package.
-
-> [!IMPORTANT]
-> [`--experimental-import-meta-resolve`](https://nodejs.org/api/cli.html#--experimental-import-meta-resolve) MUST be enabled; the feature is not really experimental—it's nonstandard because it's not relevant for browsers.
-
-```console
-$ NODE_OPTIONS="--experimental-import-meta-resolve" \
-  npx codemod@latest @nodejs/correct-ts-specifiers
-```
-
-### Monorepos
-
-For best results, run this _within_ each workspace of the monorepo.
-
-```text
-project-root/
-  ├ workspaces/
-    ├ foo/ ←--------- RUN HERE
-      ├ …
-      ├ package.json
-      └ tsconfig.json
-    └ bar/ ←--------- RUN HERE
-      ├ …
-      ├ package.json
-      └ tsconfig.json
-  └ utils/ ←--------- RUN HERE
-    ├ qux.js
-    └ zed.js
-```
-
 ## Supported cases
 
 * no file extension → `.cts`, `.mts`, `.js`, `.ts`, `.d.cts`, `.d.mts`, or `.d.ts`
@@ -111,3 +61,53 @@ const bird = new Bird('Tweety');
 const cat = new Cat('Milo');
 const dog = new Dog('Otis');
 ```
+
+> [!TIP]
+> Those using `tsc` to compile will need to enable [`rewriteRelativeImportExtensions`](https://www.typescriptlang.org/tsconfig/#rewriteRelativeImportExtensions); using `tsc` for only type-checking (ex via a lint/test step like `npm run test:types`) needs [`allowImportingTsExtensions`](https://www.typescriptlang.org/tsconfig/#allowImportingTsExtensions) (and some additional compile options—see the cited documentation);
+
+This package does not just blindly find & replace file extensions within specifiers: It confirms that the replacement specifier actually exists; in ambiguous cases (such as two files with the same basename in the same location but different relevant file extensions like `/tmp/foo.js` and `/tmp/foo.ts`), it logs an error, skips that specifier, and continues processing.
+
+> [!CAUTION]
+> This package does not confirm that imported modules contain the desired export(s). This _shouldn't_ actually ever result in a problem because ambiguous cases are skipped (so if there is a problem, it existed before the migration started). Merely running your source-code after the mirgration completes will confirm all is well (if there are problems, node will error, citing the problems).
+
+> [!TIP]
+> Node.js requires the `type` keyword be present on type imports. For own code, this package usually handles that. However, in some cases and for node modules, it does not. Robust tooling already exists that will automatically fix this, such as
+>
+> * [`use-import-type` via biome](https://biomejs.dev/linter/rules/use-import-type/)
+> * [`typescript/no-import-type-side-effects` via oxlint](https://oxc.rs/docs/guide/usage/linter/rules/typescript/no-import-type-side-effects)
+> * [`consistent-type-imports` via typescript-lint](https://typescript-eslint.io/rules/consistent-type-imports)
+>
+> If your source code needs that, first run this codemod and then one of those fixers.
+
+## Running
+
+> [!CAUTION]
+> This will change your source-code. Commit any unsaved changes before running this package.
+
+> [!IMPORTANT]
+> [`--experimental-import-meta-resolve`](https://nodejs.org/api/cli.html#--experimental-import-meta-resolve) MUST be enabled; the feature is not really experimental—it's nonstandard because it's not relevant for browsers.
+
+```console
+$ NODE_OPTIONS="--experimental-import-meta-resolve" \
+  npx codemod@latest @nodejs/correct-ts-specifiers
+```
+
+### Monorepos
+
+For best results, run this _within_ each workspace of the monorepo.
+
+```text
+project-root/
+  ├ workspaces/
+    ├ foo/ ←--------- RUN HERE
+      ├ …
+      ├ package.json
+      └ tsconfig.json
+    └ bar/ ←--------- RUN HERE
+      ├ …
+      ├ package.json
+      └ tsconfig.json
+  └ utils/ ←--------- RUN HERE
+    ├ qux.js
+    └ zed.js
+```