Just a follow-up, we have fixed the issue described in this thread:
Support component loaded via vue-loader