fix: don't generate sourcemap on build, close #831 #1113
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
|
makes sense to me but have added felix as a reviewer as he might know more |
|
The code here might also be because it was intended to publish declaration/source maps, right? Could solving that by adding it to “files” also solve your issue? |
|
The previous PR trying that way gets closed: I don't mind either ways - it's just the current state causing build tools like Vite emits a lot of warnings |
|
Thanks @antfu! |
|
Could we get a release for this? |
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.
I am not sure if sourcemaps are used somewhere, but since it's not shipped with the npm, I think it's better to not generate them otherwise would lead to hanging sourcemap reference #831