Closed mbnoimi closed 1 year ago
https://github.com/quasarframework/quasar/issues/9362#issuecomment-847992095
Don't install sass
or upgrade it yourself, rely on the version that Quasar CLI provides for you.
Are there another packages provided by Quasar?
"dependencies": {
"@headlessui/vue": "^1.7.7",
"@heroicons/vue": "^2.0.13",
"@popperjs/core": "^2.11.6",
"@quasar/extras": "^1.15.9",
"@stripe/stripe-js": "^1.46.0",
"@tailwindcss/line-clamp": "^0.4.2",
"@tiptap/core": "^2.0.0-beta.209",
"@tiptap/extension-text-align": "^2.0.0-beta.209",
"@tiptap/starter-kit": "^2.0.0-beta.209",
"@tiptap/vue-3": "^2.0.0-beta.209",
"@vuelidate/components": "^1.2.3",
"@vuelidate/core": "^2.0.0",
"@vuelidate/validators": "^2.0.0",
"@vueuse/core": "^9.10.0",
"axios": "^1.2.2",
"chart.js": "^4.1.2",
"guid": "^0.0.12",
"lodash": "^4.17.21",
"maska": "^2.1.3",
"mini-svg-data-uri": "^1.4.4",
"moment": "^2.29.4",
"pinia": "^2.0.28",
"quasar": "^2.11.4",
"v-money3": "^3.22.3",
"v-tooltip": "^2.1.3",
"vue": "^3.2.45",
"vue-flatpickr-component": "^11.0.1",
"vue-i18n": "^9.2.2",
"vue-router": "^4.1.6",
"vue3-colorpicker": "^2.1.2",
"vuedraggable": "^2.24.3"
},
"devDependencies": {
"@intlify/vite-plugin-vue-i18n": "^6.0.3",
"@quasar/app-vite": "^1.1.3",
"@rvxlab/tailwind-plugin-ios-full-height": "^1.1.0",
"@tailwindcss/aspect-ratio": "^0.4.2",
"@tailwindcss/forms": "^0.5.3",
"@tailwindcss/typography": "^0.5.8",
"@types/node": "^18.11.18",
"@typescript-eslint/eslint-plugin": "^5.48.1",
"@typescript-eslint/parser": "^5.48.1",
"@vue/compiler-sfc": "^3.2.45",
"autoprefixer": "^10.4.13",
"cross-env": "^7.0.3",
"eslint": "^8.31.0",
"eslint-config-prettier": "^8.6.0",
"eslint-plugin-vue": "^9.8.0",
"postcss": "^8.4.21",
"prettier": "^2.8.2",
"tailwind-scrollbar": "^2.1.0",
"tailwindcss": "^3.2.4",
"typescript": "^4.9.4"
},
No. But, I'd recommend removing @vue/compiler-sfc
:
https://github.com/vuejs/core/tree/main/packages/compiler-sfc#readme
Note: as of 3.2.13+, this package is included as a dependency of the main vue package and can be accessed as vue/compiler-sfc. This means you no longer need to explicitly install this package and ensure its version match that of vue's. Just use the main vue/compiler-sfc deep import instead.
Thanks a lot for the quick responses. REALLY LOVED QUASAR! This community is fantastic.
We just added a Rollup/Vite plugin to remove these errors.
https://www.npmjs.com/package/rollup-plugin-sass-migrator/v/1.0.1
We just added a Rollup/Vite plugin to remove these errors.
https://www.npmjs.com/package/rollup-plugin-sass-migrator/v/1.0.1
"rollup-plugin-sass-migrator": "^1.0.4", node_modules/@quasar/app-vite/node_modules/vite/dist/node/chunks/dep-6e2fe41e.js:39232 return plugin.buildStart.call(new Context(plugin), container.options); ^
TypeError: plugin.buildStart.call is not a function
at /home/thinkido/workspace/todo-cool-quasar/node_modules/@quasar/app-vite/node_modules/vite/dist/node/chunks/dep-6e2fe41e.js:39232:46
at Array.map (
Node.js v18.0.0
@thinkido Fixed in version 1.0.5
https://www.npmjs.com/package/rollup-plugin-sass-migrator
Thank you for report. 👍
The fix refers to vite.config, what if my project does not use vite. Is there any way to fix it?
@Vladichik what you are experiencing is most likely a separate issue. Assuming you are using Quasar CLI with Webpack, you are either stuck with @quasar/app
which is deprecated, or you are using an older version of @quasar/app-webpack
. Convert to @quasar/app-webpack
if you haven't already, and use the latest version. You must have missed reading the release notes here before upgrading the quasar
package: https://github.com/quasarframework/quasar/releases/tag/quasar-v2.14.0
What happened?
Whenever I run Quasar
quasar dev
I get many warnings related toquasar.sass
What did you expect to happen?
A clean run
Reproduction URL
https://stackblitz.com/edit/quasarframework-7eejtc?file=package.json
How to reproduce?
quasar dev
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
SPA Mode
Platforms/Browsers
Firefox, Chrome
Quasar info output
Relevant log output
Additional context
No response