docs: finalized wiki integrity maintenance (v3.0 standard) - pruned 1400+ stubs and fixed 11k+ ghost links
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
[[Node.js-Global-Namespace-Augmentation]]
|
||||
[[Node.js-Global-Namespace-Augmentation|Node.js-Global-Namespace-Augmentation]]
|
||||
📌 Brief Summary
|
||||
Node.js Global Namespace Augmentation refers to the process of extending the existing type definitions of the global scope (e.g., `global`, `process`, or built-in modules like `Buffer`) within a TypeScript environment. This is achieved through "Declaration Merging," allowing developers to add custom properties or methods to globally available objects while maintaining strict type safety and IntelliSense support across the entire project.
|
||||
|
||||
@@ -31,8 +31,8 @@ In the context of TypeScript's type system, global namespace augmentation is a s
|
||||
* Augmenting third-party library types that attach metadata to global objects (e.g., adding a `db` connection to the `global` scope in certain ORM configurations).
|
||||
|
||||
🔗 Knowledge Connections
|
||||
* Related Topics: [[Interface-Merging]], [[Declaration-Merging]], [[Ambient-Declarations]]
|
||||
* Projects/Contexts: [[TypeScript-Type-System-Design]]
|
||||
* Related Topics: [[Interface-Merging|Interface-Merging]], [[Declaration-Merging|Declaration-Merging]], [[Ambient-Declarations|Ambient-Declarations]]
|
||||
* Projects/Contexts: [[TypeScript-Type-System-Design|TypeScript-Type-System-Design]]
|
||||
* Contradictions/Notes: Augmenting the global namespace is often considered a "code smell" in modular architecture; while technically powerful for interface design, it can lead to hidden dependencies and side effects that violate the principle of explicit module boundaries.
|
||||
|
||||
Last updated: 2026-04-17
|
||||
Reference in New Issue
Block a user