Skip to content

Better errors for non-exported types #29624

Closed
#36187
Closed
Better errors for non-exported types#29624
#36187
Labels
Domain: Error MessagesThe issue relates to error messagingExperience EnhancementNoncontroversial enhancementsFixedA PR has been merged for this issueGood First IssueWell scoped, documented and has the green lightHelp WantedYou can do thisSuggestionAn idea for TypeScript
Milestone
TypeScript 3.8.1
@DanielRosenwasser

Description

@DanielRosenwasser
DanielRosenwasser
opened on Jan 28, 2019
// @filename a.ts

declare function foo(): any

declare function bar(): any;

export { bar };

// @filename b.ts

import { foo, bar } from "./a";

Currently we provide the following error messages:

Module '"./a"' has no exported member 'foo'.
Module '"./a"' has no exported member 'bar'.

We could instead provide the errors:

Module '"./a"' declares 'foo' locally, but it is not exported.
Module '"./a"' declares 'bar' locally', but it is exported as 'baz'.

Also using the

'{0}' is declared here.

related span.

Later on, we could provide quick fixes to respectively

  • Export foo from ./a.
  • Correct the usage of bar to baz.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Domain: Error MessagesThe issue relates to error messagingExperience EnhancementNoncontroversial enhancementsFixedA PR has been merged for this issueGood First IssueWell scoped, documented and has the green lightHelp WantedYou can do thisSuggestionAn idea for TypeScript

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions