You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
marking all node modules as webpack "externals", so I can get vue from a cdn and not have it as part of my build
When I loaded app, I was surprised when there were errors in my console, stating that VueClassComponent was not defined.
It would seem that the decorators are only being applied client side..
However, being that the purpose of these decorators is simply to transform the code into a vue options object, could that happen server side, perhaps as an extension to vue-loader, during the .vue compilation, removing the need for an additional client-side dependency?
The text was updated successfully, but these errors were encountered:
I was
When I loaded app, I was surprised when there were errors in my console, stating that VueClassComponent was not defined.
It would seem that the decorators are only being applied client side..
However, being that the purpose of these decorators is simply to transform the code into a vue options object, could that happen server side, perhaps as an extension to vue-loader, during the .vue compilation, removing the need for an additional client-side dependency?
The text was updated successfully, but these errors were encountered: