Needed to fix a small regression in typing.
- fix(ts): Import global symbols before using them (#7403)
Just thought I’d give everyone an update on the situation.
First and foremost, Razvan is recovering - yay! He’s over the worst of it but still unwell so will continue to be AFK until he has recovered 100%. These are the doctors and his teams (friends) orders.
That being said, we’re over the initial phase of being reactive to the situation and will now continue to provide regular updates to keep Quasar on track and at the top of it’s game.
We’ve just released an update for Quasar to bring it up to version 1.12.9 which includes a good amount of features and fixes and will continue to add fixes / features as the days go on. We are no longer only providing critical updates.
Thanks for all your well wishes to Razvan, I passed a few on to him directly and he was very touched.
Take care all,
Features and fixes to be enjoyed!
Small update to fix an issue with line endings (first release from a windows machine):
This fixes an issue experience by some using *nix based systems with nested
quasar dev in scripts.
Note: There are no direct file changes in this release. The release was to fix an issue when publishing the package on NPM from a windows based machine. Some repo changes have been made to ensure line feeds are handled correctly and the package has been re-published on NPM (hence the new version).
importStrategy: “all” is a temp work around to get your source maps working for dev; we’re not suggesting you release a production app with it. Wait for the update next week for that
I’m not sure what you mean about “restore the template”, however, the fix is in place and will stand as it’s the correct fix for this issue. If there is something else that needs changing please file a feature request on GH issues with a detailed explanation of what and why.
Scott’s point is great and summarises the teams feelings; for some more detail:
Razvan is full time on this project alone? Does he have another job or is full time really on this project?
Razvan’s main job is Quasar, the donations received for this project directly support the running and maintenance of Quasar (servers, domains, etc etc). Razvan will also do some contract work to top things up as and when but I’ll restate the point Quasar is Razvan’s main job.
if Razvan being sick holds back the project to just urgent updates
Holding back updates is our “short term” plan. Obviously with anyone taking time off, it’s never planned so we have to be reactive to the situation. The current plan is to see how Razvan is over the next week and take it from there.
Holding back updates is not a long term plan and the Quasar Team have all they need to support Quasar and provide updates with new features going forward should the need arise to do so without Razvan being around.
project getting abandoned if Razvan stops development
I and many of the core team rely on Quasar for our day to day work so this will not happen. As I’ve said, despite Razvan being the main contributor on GH, the team puts in a lot of work behind the scenes to support and grow Quasar.
I understand this is a risk you take with open source but if we make an assumption that
Razvan will not be working on this project what are the teams plan? Will someone from the team takeover as full time developer as we continue to donate to the project?
At this point in time, this is not something we’re thinking too much about. Do we have people who want to work full time for Quasar? Yes. We do. That being said, we expect Razvan to be back and working as normal once he’s rested.
It’s worth stating at this point though that we do have a disaster plan in place for Quasar to take the “bus factor” into account should the worst happen to any one of us (of course with Razvan being most crucial).
It’s important to note, the only reason we’re all here discussing this is because of how hard Razvan works. If Razvan regularly took time off (as he should) then taking a couple of weeks off wouldn’t be noticed. It’s only because he works tirelessly for Quasar and it’s community that it’s noticed.
In short - donate. Support Quasar. It hasn’t let anyone down yet and it won’t in the future.
Thanks for all your well wishes for Razvan
Take a look here: https://quasar.dev/vue-components/select#Filtering-and-autocomplete
QSelect is quite a big component so spend some time on the docs and examples.
At present no - we’ve given him strict instructions to get better and then come back. We have measures in place as a team to handle things so Razvan being around isn’t too much of an issue - it just takes us a little longer to fix things as he’s more familiar with the in’s and out’s
As far as Vue3 goes, I don’t see this having an impact at present but we will continue to update everyone as and when things change.
A fix has been PR’d for this: https://github.com/quasarframework/quasar/pull/7328
We’ll be preparing an update early next week all being well which will address this and some other PR’s .
I’ve narrowed down the cause and am making progress. Can confirm it’s definitely auto import related.
So far it seems it’s related to “auto” import of components.
Setting the value to all seems to resolve the problem - can anyone else confirm this for me please?
I think there is a balance that can be struck which can support both cases to a certain extent. Think Magento. I don’t want to turn this thread into a discussion on how to make Quasar profitable, however I do appreciate your feedback and rest assured, we have plans to get Quasar to where it needs to be to grow