text: I have a project that I have been working on for over a year, and along the way I have upgraded to the latest quasar versions each time they are available. But it seems the versions of various similar items in this older project vs a brand new quasar project are different, and I am not sure why, and whether it is safe to force update some of those. For example, running npm outdated on my old project gives me the following result:
  Whereas the newly created test project (with axios, eslint standard, i18n options selected) gives me this result:
  So the newer create one has installed later versions (but still not the latest) for some things (the three above) and actually the latest version of vue-i18n (v8.17.7) whereas my project above has an earlier version “wanted” which I don’t know why. Is it safe to force update to the later versions? How can I tell? And is it normal that these versions would not be updated when updating quasar?
  Well, I just upgraded everything by hand to match versions setup by latest quasar, fixed a bunch of new missing dependencies manually, and then went through and dealt with a ton of new eslint messages. Everything seems to work except for an odd babel-eslint error (in version 10.1.0) about not being able to read prop range of null. There is a lot of discussion on github about it, but I was able to at least turn off messages about it (in eslintrc.js) using
  
  For date, I would use the same way I would in real life: check if what I think is the month section goes above 12. So if I have date 07/24/2018 I know it’s MM/dd/yyyy because the middle number is larger than 12. Using a split activity on the string (or a substring if the format is always the same), you can split that string into 3 parts based on /, and check if the middle part is larger than 12.
  
  I’m using a local application and I wanted to explore the selectors. I launched the UiExplorer tool and indicated a button and it generated the selector. The ‘funny’ thing goes next. When I press ‘Validate’ selector, without any changes in the selector, it shows that it can’t find the UI object. The UiExplorer cannot find the selector the UiExplorer generated! How is it possible? Anyone faced it? Let me please know if you have any suggestion to troubleshoot it.