-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Closed
Labels
Qv2 🔝Quasar v2 issuesQuasar v2 issuesarea/clibug/0-needs-infoNeed more info to reproduceNeed more info to reproduceflavour/quasar-cli-vitekind/bug 🐞
Description
What happened?
If Options API selected during scaffolding then MainLayout.vue should not import ref. It should not be:
import { defineComponent, ref } from 'vue'
but:
import { defineComponent } from 'vue'
As it is today result failed with:
npm run dev
47 |
48 | <script>
> 49 | import { defineComponent, ref } from 'vue'
| ^^^
Trivial fix is to remove , ref from line 173 of quasar/create-quasar/templates/app/quasar-v2/js-vite-2/BASE/src/layouts/MainLayout.vue and from webpack / MainLayout.vue too.
What did you expect to happen?
Result of npm init quasar@latest should work, npm run dev should not fail.
Reproduction URL
https:// no URL /
How to reproduce?
- npm init quasar@latest
- select
Options API - npm run dev
- it fails:
47 |
48 | <script>
> 49 | import { defineComponent, ref } from 'vue'
| ^^^
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
Quasar CLI Commands/Configuration (@quasar/cli | @quasar/app-webpack | @quasar/app-vite)
Platforms/Browsers
No response
Quasar info output
Relevant log output
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Qv2 🔝Quasar v2 issuesQuasar v2 issuesarea/clibug/0-needs-infoNeed more info to reproduceNeed more info to reproduceflavour/quasar-cli-vitekind/bug 🐞