Fix manual enabled compilers #1457
Open
Conversation
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
digitsum
force-pushed
the
manual-enable-compilers
branch
from
8552798 to
6dbf0ca
Compare
digitsum
commented
Jan 9, 2026
| entry: ['parent.vue'], | ||
| compilers: { | ||
| vue: true, | ||
| }, |
Author
There was a problem hiding this comment.
Here the vue compiler is already automatically activated via the vue dependency in package.json. So the manual setting is not needed here and this also explains why this test is green.
That's why I created a new separate fixture. I removed the manual setting here to avoid confusion. Please let me know if this is beyond the scope of this pull request.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes the bug that manually enabled compilers as described here are not actually enabled. The config gets lost in the transformation. See provided fixture for a reproduction example.
During analysis I already found the culprit code location. That's why I directly opened a pull request to fix it. Please let me know if you prefer a different solution or if I should open an issue first.