fix(eslint): Use path.resolve for tsconfig to work around cygwin issues in Evergreen #2403
Conversation
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
…ygwin issue in Evergreen
Anemy
approved these changes
Aug 17, 2021
rose-m
approved these changes
Aug 17, 2021
|
Patch is green, merging |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Workaround for the Node.js/win32 issue that breaks eslint-typescript checks in Evergreen cygwin environment because of how windows hosts in evergreen link directories when setting up cygwin
Evergreen patch that is still running, but already passed the
checkstage that was failing before