Unspeakable Discord servers, Node's public service announcement, and making art with post-processing shaders and Pizza Rolls.

Bytes by ui.dev

Node.js 23.6 has introduced experimental support for running TypeScript files directly using the `--experimental-strip-types` mode, which requires the TypeScript syntax to be fully erasable. TypeScript 5.8 beta addresses this with a new `--erasableSyntaxOnly` flag to restrict the code to features that can be erased cleanly. This marks a significant step towards eliminating the need for a TypeScript build step and aligns with the growing trend of treating types as comments in JavaScript.

Erasing TypeScript

<pre><code>let x: string;
x = &quot;hello&quot;;
x = 100;
</code></pre>
<blockquote>
In the example above, x is annotated with the type string. Tools doing static type analysis can utilize that type, and might choose to error on the statement x = 100; however, a JavaScript engine that follows this proposal would execute every line here without error. This is because annotations do not change the semantics of a program, and are equivalent to comments.
</blockquote>
My question is: why you need types if you do not need types? JS world is amazing :)

did you guys see the errors like x,y or blah blah?.. is not a function
due to type, we don’t get prototype methods params etc.