docs: clarify export {} comment in global-modifying-module templates Improvements: #3410 (Issue)

[ishantmishra03]

docs: clarify export {} comment in global-modifying-module template ( #3410 )

Related Issue

Closes #3410

Summary

This PR improves the comment in the global-modifying-module-d-ts declaration file template by providing a clearer explanation of why the export {} line is necessary when the module exports nothing.

Problem

The original comment was:

/*~ If your module exports nothing, you'll need this line. Otherwise, delete it */
export {};

Changes Made

• Expanded the comment to clarify that export {} ensures TypeScript treats the file as a module.

• Explained the consequences of omitting the line (e.g., leaking declarations to the global scope, causing identifier conflicts).

• Included an official link to the TypeScript Handbook on module code organization.

New Updated looks like :

Notes

-- This change is documentation-only and has no impact on runtime behavior.