fix relative path resolve problem #81
Merged
Conversation
This file contains 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
pnlybubbles
changed the title
|
Looks good, thanks! |
smrq
added a commit
that referenced
this pull request
Sep 25, 2015
fix relative path resolve problem
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 an absolute path is given as entry file, a relative path will be in
row.filebased from a directory insiderow.basedir, but only relative path is given tofs.realpathSync().fs.realpathSync()uses process.cwd to resolve relative paths, so if entry files are not in the same directory with running compilation task, tsify could not find any entry files.So, I fixed this problem by resolving entry paths with the base directory before resolving real paths.