This is a bummer - any thoughts on this from the quasar folks?

For anyone finding this thread trying to use PDFJS with your quasar app, see this comment/thread https://github.com/quasarframework/app-extension-qpdfviewer/issues/5#issuecomment-518041926

Also, don’t forget to import the webpack build from pdfjs-dist
const PDFJS = await import('pdfjs-dist/webpack')

Bump on this?

I just upgraded from v1.0.0-beta.26 to latest with quasar upgrade -i. Everything seemed to work fine. But now it’s unable to find the .quasar/client-entry.js dependency. Any help appreciated

client_1  |  Dev mode.......... spa
client_1  |  Pkg quasar........ v1.0.5
client_1  |  Pkg @quasar/app... v1.0.4
client_1  |  Debugging......... enabled
client_1  | 
client_1  |  app:extension Running "@quasar/testing-unit-jest" Quasar App Extension... +0ms
client_1  |  app:extension Running "@quasar/testing-e2e-cypress" Quasar App Extension... +7ms
client_1  |  app:extension Running "@quasar/testing" Quasar App Extension... +2ms
client_1  |  app:extension Running "@quasar/qmediaplayer" Quasar App Extension... +3ms
client_1  |  app:quasar-conf Reading quasar.conf.js +13ms
client_1  |  app:dev Checking listening address availability (0.0.0.0:8080)... +5ms
client_1  |  app:quasar-conf Extension(@quasar/qmediaplayer): Extending quasar.conf... +7ms
client_1  |  App Extension (qmediaplayer) Info: 'Adding qmediaplayer boot reference to your quasar.conf.js'
client_1  |  App Extension (qmediaplayer) Info: 'Adding media-player.styl css reference to your quasar.conf.js'
client_1  |  app:webpack Extending SPA Webpack config +442ms
client_1  |  app:generator Generating Webpack entry point +7ms
client_1  |  app:dev-server Booting up... +15ms
client_1  | 
client_1  |  app:progress Compiling SPA... +177ms
client_1  |  app:progress Compiled SPA in ~693ms +694ms
client_1  |  ERROR  Failed to compile with 1 errors7:36:49 PM
client_1  | 
client_1  | This dependency was not found:
client_1  | 
client_1  | * /usr/src/client/.quasar/client-entry.js in multi (webpack)-dev-server/client?http://0.0.0.0:8080 (webpack)/hot/dev-server.js ./.quasar/client-entry.js
client_1  | 
client_1  | To install it, you can run: npm install --save /usr/src/client/.quasar/client-entry.js

I’ve got a multi select component similar to this codepen. I’d like it to auto focus on the first item in the list (the best match) in order to select quickly with the enter key rather than moving and clicking with the mouse. Any help appreciated

@patryckx thanks for the help

@patryckx looks like that works after adding emit-value and map-options, thanks! Although the model only has an array of the ids. Is there anyway to emit the entire option rather than just the id?

Hey @patryckx, thanks. I did see this section and I couldn’t get it working right, but I didn’t have emit-value or map-options. Let me give that a shot

I’m trying to set up a multi select input box using chips, pretty much exactly like this codepen: https://codepen.io/anon/pen/qeNOyG?editors=1010

Except, instead of an array of strings, I have an array of objects like so. Where I want the v-model to keep track of an array of selected objects but only display the name attribute on the chip.

const options = [{ id: 'abc', name: 'Facebook' }, { id: 'def', name: 'Google' }, { id: 'xyz', name: 'Apple' }, ... ]

This doesn’t seem like a complicated use case, but I’ve pretty much memorized the docs at this point and can’t figure out how to make this work. Any help appreciated.