Dependencies error in quasar v1.15.11, "q-date-picker" does not work.
See original GitHub issueHi, I don’t know if it will be a dependency problem, but when opening a “q-date” contained within a “q-popup-proxy” this error will appear in the console.
TypeError: Cannot read property 'months' of undefined
at H (vendor.84e27e9d.js:110)
at a.__decodeString (vendor.84e27e9d.js:110)
at a.__getViewModel (vendor.84e27e9d.js:110)
at a.data (vendor.84e27e9d.js:110)
at a.<anonymous> (vendor.84e27e9d.js:235)
at cr (vendor.84e27e9d.js:235)
at ur (vendor.84e27e9d.js:235)
at sr (vendor.84e27e9d.js:235)
at a.t._init (vendor.84e27e9d.js:235)
at new a (vendor.84e27e9d.js:235)
This causes the “datepicker” not to be displayed on the screen.
My understanding is that some packets can break the quasar. Could someone pass me their “package.json” to compare packages?
My package.json
"dependencies": {
"@quasar/babel-preset-app": "^1.1.9",
"@quasar/extras": "^1.10.4",
"@websanova/vue-auth": "^2.21.14-beta",
"axios": "^0.21.1",
"chart.js": "^2.9.3",
"chartjs-plugin-zoom": "^0.7.7",
"core-js": "^2.6.5",
"http-proxy-middleware": "^0.19.1",
"my-local-ip": "^1.0.0",
"os": "^0.1.1",
"public-ip": "^3.2.0",
"quasar": "^1.15.11",
"quill": "^1.3.7",
"quill-image-resize-module": "^3.0.0",
"socket.io": "^2.3.0",
"vue-axios": "^2.0.2",
"vue-chartjs": "^3.5.0",
"vue-clipboard2": "^0.3.0",
"vue-i18n": "^8.17.0",
"vue-router": "^3.1.6",
"vue2-editor": "^2.10.2",
"vuex-router-sync": "^5.0.0",
"webpack": "^4.44.2"
},
"devDependencies": {
"@quasar/app": "^2.2.5",
"babel-eslint": "10.0.1",
"copy-webpack-plugin": "^6.1.1",
"eslint": "^6.0.0",
"eslint-config-standard": "^12.0.0",
"eslint-friendly-formatter": "4.0.1",
"eslint-loader": "2.1.1",
"eslint-plugin-import": "2.14.0",
"eslint-plugin-node": "7.0.1",
"eslint-plugin-promise": "4.0.1",
"eslint-plugin-standard": "4.0.0",
"eslint-plugin-vue": "^6.2.2",
"html-webpack-plugin": "^4.5.0",
"strip-ansi": "^3.0.1",
"workbox-webpack-plugin": "^5.1.4"
},
"resolutions": {
"ajv": "6.8.1"
},
"engines": {
"node": ">= 8.9.0",
"npm": ">= 5.6.0"
}
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Upgrading to Quasar V2 - Dependencies, Removing CLI ...
We'll start going through the guide, and run into some upgrade errors along the way!...This gives me a chance to share some Vue3...
Read more >QDate - Quasar Framework
The QDate Vue component provides a method to input dates from Gregorian or Persian calendars.
Read more >quasar-app-extension-qdatetimepicker - npm
Vue Property Type Description
prefix String Prefix
suffix String Suffix
filled Boolean Use filled design for the field
Read more >react how to use useeffect Code Example - Code Grepper
useEffect is a hook for encapsulating code that has 'side effects,' and is like a combination of componentDidMount , componentDidUpdate , and ...
Read more >dot_filenames.txt - Index of /
Issues .jffs2_for_pc.tar.bz2 .sql_2016-6-1.zip .sunos4 .data.in .simp . ... .2.10-src.zip .7.6-jar-with-dependencies.jar .boundary.error.example.png ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@DengnisR The best thing you can do at this point is to create a CodePen.
@hawkeye64 @metalsadman Thank you very much for the contribution. But I already managed to fix the problem.
As mentioned in the comment above, I use the “i18n” package to manage my translations, the problem is that I was using this as the main translator of my application, so components that have translations choose to search first in the custom translations of “i18n” than in quasar translation packages.
All you have to do is add the “date” object with the translations to my translations file. Just as you mentioned. The problem with the days appearing the same in each month was due to the fact that a couple of indices were missing from the date object.
These in particular.
Adding them to the “date” object resolved the agenda issue.
This does not eliminate the fact that removing the “locale” directive in the “q-date” component should work with the translation of the quasar. But it seems that the package “i18n” causes this conflict.