Give a better error message when an import isn't found but a namespace of the same name exists

foo.d.ts

declare module foo {
    // ...
}

bar.ts

import foo = require("foo");

"foo" won't be found, but if the compiler can resolve an identifier named foo to a namespace that uses the declare module syntax, we should probably give an error like

Cannot find module 'foo'.
  A legacy-style namespace with the same name was found.
    Try changing the declaration to use quotes (e.g. 'declare module "foo"').

Somewhat skeptical that turning the namespace declaration into an external module declaration is the most likely fix. I feel like people making this error are more likely writing global code and thinking they need to do some incantation to access things across file boundaries

I think as soon as you see an import, you can figure the user is trying to use modules, but I see what you're saying.

I don't think we need to do this

Navigation Menu

Repository navigation

Give a better error message when an import isn't found but a namespace of the same name exists #10464

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Give a better error message when an import isn't found but a namespace of the same name exists #10464

Description

Activity

RyanCavanaugh commented on Aug 22, 2016

DanielRosenwasser commented on Aug 24, 2016

RyanCavanaugh commented on Aug 25, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions