Add noResolve option to TypeScript compiler options - #741
Open
vancez wants to merge 1 commit into
Open
Conversation
|
I'm also seeing this issue on MacOS |
nielsvaneck
approved these changes
Apr 10, 2026
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
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.
src/test.proto
protoc --ts_out ./ --ts_opt generate_dependencies,long_type_string,output_javascript --proto_path ./src ./src/test.protoUsing the above command will generate the following files:
If you change the
idfield toid2and then run the command again, thetest.d.tsfile will not be modified.If the
noResolveoption is enabled,test.d.tswill be generated correctly.This issue only occurs on Windows; there is no such problem on Linux or macOS.