This sounds reasonable to me! Thanks for extracting my comments into an actionable issue :D

Next Steps

1. Nest.js Quick Start guide:

• update code snippets to only be TypeScript
• create a new Step "Capturing Nest.js Errors" and move the exception filter content there

Note: To help with the maintainability of these changes, I updated the Nest.js's quick start guide to no longer inherit content from getting-started-node. Quick Start guide content is now in docs/platforms/javascript/guides/nestjs/index.mdx

-> see PR #13497

2. Installation Methods

• the CommonJS guide can link to the quick start guide (note: content currently comes from a shared CommonJS page (node?))
• review and update information on other subpages to make sure it's correct (especially content that's inherited from Node pages)

I'm already working on 1)

How do you think we should proceed with 2)?
Would you have time to review these pages (we can also do it together -- I'm not sure what's more efficient)?

@inventarSarah

How do you think we should proceed with 2)?

• Agree we can link to quick start from the CommonJS page
• The ESM pages (snippets) just need to be adjusted to Nest

I agree with Charly

Agree we can link to quick start from the CommonJS page

we can just create the nest specific version that links to QS (and doesn't show much more, if anything)

The ESM pages (snippets) just need to be adjusted to Nest

+1 -- we can either duplicate the pages for Nest or adjust the code snippets. No strong opinions.

One more thing: I'd probably also slightly adjust the "How to Decide Which Instal. Method to use" section and mention NestJS. For example, add a subsection that reads something like:

My application is a simple/default NestJS app

By default, NestJS transpiles to CJS, so you should follow the CJS instructions. Keep reading if you have a more customized application or build setup.