Skip to content

no-legacy-imports should account for more recent exports #10394

@runspired

Description

@runspired

We added (and thus exposed via *) some exports, mostly types. We should either (A) also account for new exports added over time in our book-keeping or (B) say the older packages have their exports frozen entirely and to gain access to new things you must shift. I suspect (A) is better, and what we should do is create a mapping of file-to-file for any unknown tokens so we aren't constantly updating the list.

We also don't error for legacy import paths if they import tokens not in the current list - we should.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions