-
Notifications
You must be signed in to change notification settings - Fork 20
export default {} works differently than module.exports = {} #5
Comments
This occurred to me when I changed from laravel-elixir-vue to laravel-elixir-vue-2. My components props were not set. When I changed exports default to module.exports it works. Weirdly enough, on laravel-elixir-vue, exports default works just fine. 😞 |
I think it's the same thing as in JeffreyWay/laravel-elixir-vue#10 For this to work this package would need to use babel loader for .js files and add "babel-plugin-add-module-exports" as dependency, although the current ES proposal is using "default" as in require('./components/Example.vue').default, or that's why I understand (not versed on node/js enviroment). |
@osiux Thanks for the response, will try and confirm the results later 👍 |
Checking in to report that going from vue 1 to 2 after following the vue 1 laracasts, I had to change all my single file components to module.exports from exports default. exports default no longer worked for me either; none of my properties came up defined. |
@osiux I can't seem to get that done lol ( I'm also not versed on node) 😆 . But what I can confirm is that after getting a fresh laravel 5.3, it works out of the box for me. Maybe this didn't work because there is an issue with migrating from vue 1 to vue 2. I can only assume that's the case because laravel 5.3 came with vue 2 support |
When using
exports default { ... }
,require('./components/Example.vue')
returns object withdefault
key as content.Returns
Returns
Shouldn't these two examples work the same way?
The text was updated successfully, but these errors were encountered: