set NODE_ENV=production for volar #218
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
predragnikolic
approved these changes
Feb 4, 2024
|
Note that we could not avoid |
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.
Using Volar in a project with latest Vue version (2.7.16) reveals an issue when using
transitionelement that is caused by the fact that@vue/compiler-domruns in a non-production mode.Volar VSCode extension doesn't show this issue because it bundles its whole code with NODE_ENV set to "production". We could do the same in this package which would make installation faster, server code smaller and would not require running
npm install(which can avoid some problems) but that's more effort.See also vuejs/language-tools#3881 for more detailed explanation of the issue.