It was renamed to boot because people were getting them confused with Quasar plugins (like Dialog).
It also make sense because you can use Vue.use before Vue is instantiated.

@quasar/quasar-app-extension-qmediaplayer v1.0.0-beta.1 Release!
We’re now beta!
Updated examples on readme.
Test website changed to:
https://qmediaplayer.netlify.com
https://github.com/quasarframework/app-extension-qmediaplayer/releases/tag/v1.0.0-beta.1

@quasar/quasar-app-extension-qflashcard v1.0.0-beta.1 Release!
We’re now beta!
Test website has changed to:
https://qflashcard.netlify.com
https://github.com/quasarframework/app-extension-qflashcard/releases/tag/v1.0.0-beta.1

1. There have been instances when Yarn borks everything up globally. If you haven’t hit it yet, then don’t worry about it until you do.
2. Yarn puts globals into it’s own location, thereby excluding use of Node Versioning toolsets, like NVM.

At work, we have 4.5.3, 5.0/5.1 and (upcoming) 6.0 versions of our product, each of versions are using different versions of Node and associated NPM packages, so I have to use NVM to manage all that.

quasar new b <boot file name>

If you are using Quasar v1-beta, you can use the dotenv app extension: https://github.com/quasarframework/app-extension-dotenv

Yarn is the only way to go. Continue to use npm for globals, though.

Added new property no-controls. This turns off the controls window altogether. Beneficial if you want full control and have your own controls elsewhere on your page.

https://github.com/quasarframework/app-extension-qflashcard/releases/tag/v0.0.1-alpha.12

Quasar is for front-end. Database packages would be for a back-end. You need to build out a back-end to consume MySQL and communicate to/from front-end to back-end.