Add typesVersions for resolving all type imports using legacy moduleResolution #636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When TS is set up to not use a
moduleResolution
ofnode16
orbundler
yet (like legacynode
/node10
), then TS would not look intoexports
.There is
types
, but that only works when resolving the main index module, likeimport from 'ember-cli-page-object'
, but all other submodules likeember-cli-page-object/adapter
would fail to resolve totypes.d.ts
.This is removing
types
in favor oftypesVersions
, supporting the same wildcard-matching thatexports
does.