-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Example app should use runtime-only version of vue? #300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@RavenXce Feel free to make a PR please 👍 Looks good to me |
This gives a better convention to start users of with - all templates are pre-compiled through webpack/vue-loader, and the runtime-only version of vue is imported instead. Resolves rails#300.
This gives a better convention to start users of with - all templates are pre-compiled through webpack/vue-loader, and the runtime-only version of vue is imported instead. Resolves #300.
Possibly related, possibly worth a new issue (possibly worth telling me I'm Doing It Wrong)… I tried to modify the new example to use vue-router. Could never get past Considering vue-router (and vuex) are staples…I'd love to see an example that shows what I'm doing wrong. |
That doesn't seem related to this issue. Did you add the component during initialization?
Reference: https://vuejs.org/v2/guide/components.html#Local-Registration |
I finally got a router to work within the context of webpacker (example: https://github.com/irrg/rails-webpacker-vue-example) but I haven't been able to port my Vue into it yet. I'll figure it out and if needed ask help elsewhere. That said, the moment I tried to add hot reloading to my linked example, vue-router broke again. So some stuff definitely feels fickle, but it's likely outside of the scope of the webpacker project (and probably firmly in webpack's camp). |
This gives a better convention to start users of with - all templates are pre-compiled through webpack/vue-loader, and the runtime-only version of vue is imported instead. Resolves rails/webpacker#300.
This gives a better convention to start users of with - all templates are pre-compiled through webpack/vue-loader, and the runtime-only version of vue is imported instead. Resolves rails/webpacker#300.
This gives a better convention to start users of with - all templates are pre-compiled through webpack/vue-loader, and the runtime-only version of vue is imported instead. Resolves rails/webpacker#300.
The hello world example app is currently referencing the full version of vue which includes the compiler. This isn't really needed and isn't the default way of running Vue applications (
import Vue from 'vue'
defaults to the runtime version).Should the example use this style instead? : vuejs-templates/webpack#215 (comment)
The text was updated successfully, but these errors were encountered: