docs: clarify TypeScript type stripping behavior

[Herrtian]

Summary:

• Explain what type stripping does in the native TypeScript guide.
• Clarify that Node.js does not type check TypeScript files at runtime.
• Mention tsc --noEmit for type checking.

Verification:

• npm run format:check -- pages/typescript/run-natively.md
• npm run lint -- pages/typescript/run-natively.md
• npm run build

Refs: #34

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nodejs-learn	Ready	Preview	May 23, 2026 12:18pm

[cursor]

PR Summary

Low Risk
Low risk documentation-only changes clarifying runtime behavior; no code or API behavior is modified.

Overview
Clarifies the native TypeScript guide to explain that Node.js runs .ts files via type stripping (removing erasable TS syntax) rather than full transpilation.

Adds explicit guidance that Node.js does not type check at runtime and recommends running npx tsc --noEmit separately, plus expands the constraints section with dedicated Type stripping and Type checking explanations and examples of non-erasable syntax (e.g., enum, namespaces) requiring --experimental-transform-types or other tooling.

^{Reviewed by Cursor Bugbot for commit f1b2e1c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

👋 Codeowner Review Request

The following codeowners have been identified for the changed files:

Team reviewers: @nodejs/typescript

Please review the changes when you have a chance. Thank you! 🙏