improve ts guides

Author: avivkeller

apps/site/pages/en/learn/typescript/introduction.md

@@ -73,8 +73,9 @@ These type definitions allow TypeScript to understand Node.js APIs and provide p
 ```js
 import * as fs from 'fs';
 
-fs.readFile('example.txt', 'foo', (err, data) => {
-  //                          ^^^ Argument of type '"foo"' is not assignable to parameter of type …
+fs.readFile('example.txt', foo, (err, data) => {
+  //                       ^^^
+  // Argument of type '"foo"' is not assignable to parameter of type …
   if (err) {
     throw err;
   }

apps/site/pages/en/learn/typescript/publishing-a-ts-package.md

@@ -126,9 +126,9 @@ A note about directory organisation: There are a few common practices for placin
 The purpose of types is to warn an implementation will not work:
 
 ```ts
+// @errors: 2322
 const foo = 'a';
 const bar: number = 1 + foo;
-//    ^^^ Type 'string' is not assignable to type 'number'.
 ```
 
 TypeScript has warned that the above code will not behave as intended, just like a unit test warns that code does not behave as intended. They are complementary and verify different things—you should have both.

packages/rehype-shiki/src/index.mjs

@@ -24,7 +24,7 @@ const { shiki, getLanguageDisplayName, highlightToHast, highlightToHtml } =
       transformerTwoslash({
         langs: ['ts', 'js', 'cjs', 'mjs'],
         // Don't throw on errors on untype-able code
-        // throws: false,
+        throws: false,
       }),
     ],
     // We use the faster WASM engine on the server instead of the web-optimized version.