Fix usage of components imported from other files #10
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.
currently, importing a component from another file does not work, eg;
In
main.vue
In
other.vue
After investigation, this is because the template-compiler isn't aware that
Other
is an imported component, so the template code is generatingresolveComponent("Other")
instead ofcreateVNode(Other)
.The fix is simply to tell the template compiler about the variables exported from the setup script (via
bindingMetadata
)Be aware; When testing, meteor will keep caching files even if the compiler is updated, it's useful to run
meteor reset
after changing the compiler so that all files are built with the new version.