Does this extension work in recent version of Quasar?
absantanna2412 opened this issue · comments
I tried to use this extension in latest stable version of Quasar 1.12 and got this error
ERROR Failed to compile with 1 errors 14:22:36
error in ./node_modules/quasar-app-extension-qdatetimepicker/src/services/render.js
Module build failed (from ./node_modules/@quasar/app/lib/webpack/loader.transform-quasar-imports.js):
Error: Unknown import from Quasar:
- imports.js:179 module.exports
[backstage]/[quasar]/dist/babel-transforms/imports.js:179:11
- loader.transform-quasar-imports.js:17
[backstage]/[@quasar]/app/lib/webpack/loader.transform-quasar-imports.js:17:38
- Array.map
- loader.transform-quasar-imports.js:9
[backstage]/[@quasar]/app/lib/webpack/loader.transform-quasar-imports.js:9:6
- String.replace
- loader.transform-quasar-imports.js:6 Object.module.exports
[backstage]/[@quasar]/app/lib/webpack/loader.transform-quasar-imports.js:6:37
@ ./node_modules/quasar-app-extension-qdatetimepicker/src/component/QDatetimePicker.js 4:0-80 355:23-29
@ ./node_modules/quasar-app-extension-qdatetimepicker/src/boot/qdatetimepicker.js
@ ./.quasar/client-entry.js
@ multi (webpack)-dev-server/client?http://0.0.0.0:4200 (webpack)/hot/dev-server.js ./.quasar/client-entry.js
My dependencies:
"dependencies": {
"@quasar/extras": "^1.8.1",
"axios": "^0.19.2",
"quasar": "^1.12.2",
"sass-convert": "^0.5.2",
"vue": "latest",
"vue-i18n": "^8.0.0",
"vuex": "^3.4.0"
},
"devDependencies": {
"@quasar/app": "^1.9.3",
"babel-eslint": "^10.0.1",
"eslint": "^6.8.0",
"eslint-config-standard": "^14.1.0",
"eslint-loader": "^3.0.3",
"eslint-plugin-import": "^2.14.0",
"eslint-plugin-node": "^11.0.0",
"eslint-plugin-promise": "^4.0.1",
"eslint-plugin-standard": "^4.0.0",
"eslint-plugin-vue": "^6.1.2",
"quasar-app-extension-qdatetimepicker": "^1.0.0-rc.10"
},
"engines": {
"node": ">= 10.18.1",
"npm": ">= 6.13.4",
"yarn": ">= 1.22.4"
},
"browserslist": [
"last 1 version, not dead, ie >= 11"
],
"resolutions": {
"@babel/parser": "7.9.6"
}
thx for report.
I was only able to reproduce the mentioned error after enable the modern build
feature.
If for some reason, that error also occurs while doing a legacy build, pls let me know.
anyway, update the extension to the latest version and try again.
Hi Tobias,
With modern disabled, I was able to build without problems. I'll wait for the fix to use modern build again.
Thanks.
So, update the extension to the latest version (1.0.0-rc.11) and try again.
Yeah I just saw, tried and worked. Thanks again. For me it's closed