-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Fails to work with Vue < 2.1.5 #96
Comments
Sorry for the late reply, but this sounds like this might be an issue with keen-ui/vue-icons as it could be related to a recent VueJS release.
|
But I am getting this error with the default electron-vue project without having added any other packages. Edit: I've tried fixing ALL versions in the package.jsons to their lowest values and still got the error. This is the part I don't understand. |
Okay after experimenting, this is how I got it to work. This essentially reverts developer dependency versions before the breaking changes. In |
That fixed everything, thanks! I thought it had something to do with vue-loader but I lacked fu to get it going myself. |
Uh oh!
There was an error while loading. Please reload this page.
Found an issue or bug? Tell me all about!
Describe the issue / bug.
#
When using a Vue version in /app lower than 2.1.5, running dev results in:
[Vue warn]: Error when rendering component at D:\David\Documents\my-project2\app\src\components\LandingPageView.vue:
Uncaught TypeError: _vm._v is not a function
How can I reproduce this problem?
#
Use vue-cli to init a fresh new project, with Vue 2 and all optional packages enabled except for Vue-Resource (didn't try with a different setup). Disable eslint and testing setup. Next, before using npm install, change the package.json in /app to specify "2.1.4" for Vue instead of "^2.0.1". Then
npm install
andnpm run dev
.If visual, provide a screenshot.
#
http://i.imgur.com/UYk1wbm.png
Tell me about your development environment.
Right now I'm in a bit of a pickle because vue-icons is currently only working with Vue <= 2.1.4 until it's updated and I need a similar version of Vue for Keen-UI (although this will likely be updated within a few days). I had everything working with an older version of Vue (something like 2.0.3) but accidentally updated both package.jsons and when I tried to reverse the process, I came across this problem.
The text was updated successfully, but these errors were encountered: