Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
V3RON
force-pushed
the
feat/add-tsconfig-resolution
branch
from
45c4dca to
ed502b4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
This pull request adds a new resolver to the resolution chain that looks up dependencies based on the paths defined in the
tsconfigfile. This behavior is consistent with Expo's internal resolver, so if you use path aliases in your Expo app, you’ll be able to use them with Harness as well.Testing
Ran Harness in an Expo-based project using alias-based imports in a test file.