search

qlik-demo-team / qdt-vue-template

A simple Vue.js template that uses Qdt-components
10 stars 4 forks source link

Module build fails #1

Closed miranda-elliott closed 6 years ago

miranda-elliott commented 6 years ago

Module won't build. Tried re-installing vue-loader and updating vue-template-compiler. How can this be resolved? Thank you.

Module build failed: Error:

Vue packages version mismatch:

- vue@2.5.2
- vue-template-compiler@2.5.17

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using vue-loader@>=10.0, simply update vue-template-compiler.
If you are using vue-loader@<10.0 or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the l
test.
jdriesen commented 6 years ago

In case smb is interested ... I succeeded in modifying the package.json file.... Right now, I've everything working like a charm ...

yianni-ververis commented 6 years ago

Thank you Johhny. Can you commit the package.json?

jdriesen commented 6 years ago

mmm ... my App was running last week, now not anymore ... Gonna check what happened.

Coming back on this asap.

jdriesen commented 6 years ago

If I can ask ... did smt change on DATA side ? As soon as I click on a component, I get the spinner ... (and this was not the case last week...)

Thanks in advance for your reply, Johnny

yianni-ververis commented 6 years ago

You have updated your packages so I do not know about any conflicts.

This is working fine, https://webapps.qlik.com/qdt-components/vue/index.html#/

jdriesen commented 6 years ago

I agree ... I updated the packages ... Though, the data is taken from const options = { config: { host: 'sense-demo.qlik.com', secure: true, port: 443, prefix: '', appId: '133dab5d-8f56-4d40-b3e0-a6b401391bde', }, connections: { vizApi: true, engineApi: true, }, };

(this is set in file QdtComponent.vue)

So, I thought maybe smt is changed at data side ...

Grtz, Johnny

jdriesen commented 6 years ago

I think I found the cause ... (but I don't know what to do about it)

As far as I remember, this was not the case last week ....

error

yianni-ververis commented 6 years ago

close all webpack running services and rerun. The port you are using is not in the VP Whitelist.

You should point to your Qlik Server where you manage the Virtual Proxy.

miranda-elliott commented 6 years ago

Fixed by running npm install vue@2.5.17. The latest vue-template-compiler version is 2.5.17 so needed to downgrade from vue 2.5.2.