Typesafety: Fix vite-node resolution in TS plugin #12039
Merged
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.
Note, this is a PR to #12019.
Within the context of the TS plugin running within my editor, the root directory of the vite-node server was
"/"
rather than the project directory.It looks like this is because it was defaulting to the current working directory, which is different in a TS plugin context compared to regular Vite / CLI usage. If I log
process.cwd()
within the TS plugin, I get"/"
.The fix was to explicitly pass our resolved root directory to vite-node rather than relying on cwd by default.