Remove 'source-map-support' package in favor of Nodejs built-in source mapping feature

[micalevisk]

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe it

as of now @nestjs/cli injects source-map-support. But as they say in their README:

we can use nodejs's --enable-source-maps flag instead since nodejs v12

I don't know why this package was added since v12 is too old, to be honest 🤔

Describe the solution you'd like

update the following lines to replace -r "source-map-support/register" with --enable-source-maps

nest-cli/actions/start.action.ts

Lines 178 to 181 in d87405a

	const sourceMapsRegisterPath = this.getSourceMapSupportPkg();
	if (sourceMapsRegisterPath !== undefined) {
	processArgs.unshift(`-r "${sourceMapsRegisterPath}"`);
	}

I tested this is a simple nestjs app and it seems to be working:

code

when sourceMap:true in our tsconfig

when sourceMap:false in our tsconfig

Teachability, documentation, adoption, migration strategy

No response

What is the motivation / use case for changing the behavior?

1. source-map-support looks abandoned. Their github repository has many PRs and issues open
2. it has issues such as Error cause is not logged in dev:watch mode #2533 that @nestjs/cli cannot work around
3. we would have one less dependency on @nestjs/cli

[kamilmysliwiec]

Would you like to create a PR for this issue?