Topics created by valasek

yarn dev is running your dev script from your package.json. This script is doing the env for node, before Quasar is started so it can be accessed in that instance. quasar dev by itself has no hooks for this and your package.json scripts are not called.

thanks @tohagan I’m working on polishing the rough edges and would love to have it on Quasar Awesome. I’m still very new to working with Quasar but I love the idea and it has been a joy to work with so far. @valasek thanks for adding my project to the starter kit list here. I’m trying to follow best practices from documentation and get advice from people who are experts in the various areas that it touches on. Hopefully I can share my experiences and lessons learned and get more people to try out Quasar!

Hi: I have the same problem as you. I have verified that if I put the component inside a v-for it does not work. With this check I assumed that ref must be an array not a single value. (https://stackoverflow.com/questions/52086128/vue-js-ref-inside-the-v-for-loop) So my solution was:   <template v-for = “(item, i) in items”> …    <q-popup-proxy ref = “MyReferences”>           <q-date              …              @input = “() => $ refs.MyReferences [i] .hide ()”           />   </q-popup-proxy> … </template> Where i = 0,1,2, … I do not know if in your case this helps you, but to me your doubt helped me to solve mine, thanks

Great work @valasek .

@stukki Thanks a lot, I try on my project but 3 vuex errors returns when send a file (store/uploader/action) : [vuex] unknown local mutation type: MutationOnUploadProgress, global type: uploader/MutationOnUploadProgress [vuex] unknown action type: app/ActionUploaderDialog [vuex] unknown local action type: ActionAfterFileUpload, global type: uploader/ActionAfterFileUpload Could you help me ?

Thank you fixed using v-model option.