https://docs.npmjs.com/cli/link is the proper way, IMHO

@alegreiff use git perhaps?

@dewdad: I’m a newbie when it comes to npm / node, but what I do to use quasar dev is: make a separate clone of the quasar repo, run npm install / npm run build / npm link, then go to my project folder and run npm link quasar-framework. Although I think it’s possible to use the quasar-edge package instead of that?

Another way: you could treat the whole modal as an input. Pass a v-model to the modal and follow the protocol to signal its change (this.emit('input', value)), see the vue.js section on custom inputs

Sorry, no worries, I was able to patch things on the Kinto side, using an event subscriber. I’ll add a ticket as a reminder. Anyway, it’'s just an edge case, where Kinto-attachment expects that submited forms only have “valid” fields, from its point of view, but quasar adds that field without an opportunity to tweak that.

I’m testing Quasar’s v0.14 uploader together with kinto-attachment (an attachment plugin for Kinto storage) and there is a problem.

The problem sits with both Quasar and Kinto:

• in the uploader, there is a line:

form.append('Content-Type', file.type || 'application/octet-stream')

The form is then sent with xhr.send(form). There is no insertion point where that form can be further customized (so that I can remove the unwanted Content-Type field.

• in kinto (irelevant for this) there will be an error when not all form fields are processable.

I’ll address this problem to the Kinto maintainers, also, but there it may have bigger implications and that code be aligned with some package philosophy. Here, in Quasar, at least, maybe it’s possible to somehow register a “modifier” for the form, before it’s submitted? Or make the Content-Type field optional?

@GameSomnic see https://github.com/quasarframework/quasar/blob/dev/dev/components/test-layout/layout.vue#L4

So basically, now you just toggle the left slot and fill it with whatever the sidebar you want:

https://github.com/quasarframework/quasar/blob/dev/dev/components/test-layout/layout.vue#L34

Is the timeline component still in for v0.14? I haven’t found it.

Also, @rstoenescu I really think you should release 0.13 as 1.0 and 0.14 as 2.0, the code and quality is there, there’s no reason to be shy about it.

Maybe this can help you: https://play.pixelblaster.ro/blog/2017/03/02/analyse-and-optimize-a-webpack-vuejs-bundle/