Skip to content

Remove restriction on external module augmentations introducing new top-level names #8478

@RyanCavanaugh

Description

@RyanCavanaugh

Module augmentation cannot introduce new names in the top level scope

This error is stopping us from accurately representing UMD-augmenting modules like moment-range. While it's a correct restriction for ES6 values, it's not correct for legacy modules, nor is it a correct restriction for types (e.g. you might want to write an interface in a module augment to provide a type of a new overload parameter)

Metadata

Metadata

Assignees

Labels

@typesRelates to working with .d.ts files (declaration/definition files) from DefinitelyTypedBugA bug in TypeScriptFixedA PR has been merged for this issue

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions