Closed GastroGeek closed 4 years ago
This is because vuese
only treats export default {}
as a component. But I don't understand why you use named export?
OK, here goes...
Personal taste? consistent conventions? multiple exports? Refactoring large codebases where you may temporarily have said multiple exports from an SFC? the man himself added it to vue-loader (so again, consistency in the broader sense)? Tree shaking in certain scenarios? Because I am adding please to the request?
https://github.com/vuejs/vue-loader/releases/tag/v13.6.0
But seriously, this tool is great so thank you for making it regardless of your decision to allow named exports.
PS - Please allow named exports 👍
Thanks for your information, I will seriously consider it.
test should pass https://github.com/vuejs/vue-loader/issues/1080
will be finished by #159
will be released next version, if you have any question you could reopen it
Describe the bug
To Reproduce Steps to reproduce the behavior: Use the cli tool to parse a single component 'IButton.vue' => 'IButton.md'. Nothing especially fancy. Component content is:
Expected behavior It should still work and generate all props, slots etc info
Which version do you use: "@vuese/cli": "^2.0.1"