Excellent, it worked. I had some old conf.js files…

Thank you!

@Akaryatrh Thanks for the tip, I removed the local quasar-cli and reinstalled, now all is good. As you say, quite a change

I’m trying to get autocomplete to work with the chips input. However, the search method never seems to get hit… should this work at all or is autocomplete only for the text input field?

Hi I also have a project on 0.14 in TypeScript and am looking for pointers how to achieve that with 0.15. I suppose one would have to put the TypeScript loaders into quasar.conf.js? Anyone have any ideas on this?

@Akaryatrh Thanks for the tip, I removed the local quasar-cli and reinstalled, now all is good. As you say, quite a change

Well done! I have however updated my quasar-cli and run a “quasar init bla” and it still creates a 0.14.9 quasar app… is this my installation or a general problem?

I guess I should open an issue on github then…?

Hi
I’m using

<q-input v-model="thefile" @change="onFileChange" type="file"/>

and

  onFileChange(e) {
      debugger;
    let files = e.target.files || e.dataTransfer.files;
    if (!files.length) {
      return;
    }
    this.createInput(files[0]);
  }

in the component. However, neither ist “thefile” bound to the input value, nor is the onFileChange method triggered. Any pointers on what I am doing wrong?

I’m trying to get autocomplete to work with the chips input. However, the search method never seems to get hit… should this work at all or is autocomplete only for the text input field?

Excellent, it worked. I had some old conf.js files…

Thank you!

Hi, is this a problem from my upgrade or is it a bug that the index property is missing in the beta template in the file config/index.js?
It used to be:

 index: path.resolve(__dirname, '../dist/index.html'),

and my

quasar build 

won’t work because of this…
Regards
Greg