Home Original page

docs(learn): expand type stripping explanation and constraints by ibiraza1077-pixel · Pull Request #8726 · nodejs/nodejs.org

Conversation

@ibiraza1077-pixel

Description

Expands the run-natively page to address the request for a more in-depth conceptual explanation of Node.js type stripping, as requested in #7440.

Changes:

  • Adds a "What is Type Stripping?" section explaining the concept and how it differs from transpilation
  • Adds a version support table covering v22.6.0 through v23.6.0
  • Completes the Constraints section, which previously contained an incomplete sentence with no list

No existing content was removed or restructured.

Validation

This is a documentation-only change. Reviewers can verify by previewing the markdown renders correctly and checking the version numbers against the Node.js changelog.

Related Issues

Addresses #7440

Check List

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run pnpm format to ensure the code follows the style guide.
  • I have run pnpm test to check if all tests are passing.
  • I have run pnpm build to check if the website builds without errors.
  • I've covered new added functionality with unit tests if necessary.
Expands the run-natively page to address the request for more in-depth
explanation in nodejs#7440.

Changes:
- Adds a "What is Type Stripping?" section explaining the concept and
  how it differs from transpilation
- Adds a version support table covering v22.6.0 through v23.6.0
- Completes the Constraints section, which previously contained an
  incomplete sentence with no list

No existing content was removed or restructured.

Signed-off-by: ibiraza1077-pixel <ibiraza1077@gmail.com>

@vercel

@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! 🙏

avivkeller

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has several unrelated changes, and fails to provide any additional information that isn't mentioned previously.

Simply re-stating information doesn't resolve any open issues.

@ibiraza1077-pixel

Thank you for the feedback. I understand — the additions were
accurate but largely restated information available elsewhere.

Could you point me toward what genuinely new content would be
most valuable to add? For example, would an explanation of why
Node.js chose type stripping over full compilation, or guidance
on native running vs transpilation tradeoffs, be the right
direction?

@JakobJingleheimer

I think the info is scattered around. It would likely take a lot of digging to find (and would be faster for someone who's already familiar to make the updates—probably me or Marco).

I think this is not a "good first issue" 😅