Skip to content

docs(learn): expand type stripping explanation and constraints#8726

Open
ibiraza1077-pixel wants to merge 1 commit intonodejs:mainfrom
ibiraza1077-pixel:main
Open

docs(learn): expand type stripping explanation and constraints#8726
ibiraza1077-pixel wants to merge 1 commit intonodejs:mainfrom
ibiraza1077-pixel:main

Conversation

@ibiraza1077-pixel
Copy link

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>
@ibiraza1077-pixel ibiraza1077-pixel requested a review from a team as a code owner March 16, 2026 12:03
@vercel
Copy link

vercel bot commented Mar 16, 2026

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

Project Deployment Actions Updated (UTC)
nodejs-org Ready Ready Preview Mar 16, 2026 0:04am

Request Review

@github-actions
Copy link
Contributor

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

Copy link
Member

@avivkeller avivkeller left a comment

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
Copy link
Author

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
Copy link
Member

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" 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants