fix: error when css calls reference css calls inside components #971
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.
Motivation
fix: #957
Summary
The issue was caused by the referenced template getting hoisted, converting the path already added to
state.queue
into an identifier referencing the hoisted variable. The code processing the queue expected all paths to be tagged template literals and crashed when trying to accesspath.get('quasi').get('expressions')
.Avoiding hoisting templates when referenced in other templates seem to have solved the problem.