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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: migrate jest-resolve to TypeScript #7871
chore: migrate jest-resolve to TypeScript #7871
Changes from all commits
7d70b2f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this makes the most sense - the constructor of
jest-resolve
takesModuleMap
fromjest-haste-map
. So both for types but also for usage, we need to ensure that the API is what we expect it to beThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
built
haste-map index.d.ts
:totally missing the main export.
Working on how to fix this atm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure we can fix this without dropping the
export type
s at the top of haste map. Basically, we want bothexport = HasteMap
(because making it the default export like it should be would be breaking) andexport type ...
. It would be fine for a normal property (can just put it on the class), but I don't know how we could possibly put types ontoHasteMap
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for digging! I say we keep it as is then, and try to go for a real ESM run at some point in the future.
It's easier with modules like haste map anyways since it's mostly internal and not pluggable like other parts of Jest are
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Guess the
ModuleMap
andHasteFS
types are more important anyway, they're the ones used inContext
etc