Quasar v0.15 is out!
-
This post is deleted! -
@rstoenescu Thanks for your hard work on the 0.15 update. I really appreciate the effort that went into building comprehensive documentation. It really shows how much work you put into it! Well worth the wait.
I’ll check with my manager if we can support you on your Patreon page, as you certainly deserve it!
-
Bravo! Can’t wait to migrate…
-
Well done! I have however updated my quasar-cli and run a “quasar init bla” and it still creates a 0.14.9 quasar app… is this my installation or a general problem?
-
Woooohooooow! Good job!
-
@gregorybleiker I guess It’s your local installation. I just tried it and ended with a
Running on Quasar v0.15.0app. It’s quite confusing BTW not to have anymore quasar framework onpackage.jsonfile ^^ (onlyquasar-clion dev deps)You might reinstall
quasar-climaybe It would solve the issue. -
Bummer! Just started quasar last week, read through doc, playing various starter kits and components, now look like I need to re-read! Hope 0.15 is easier and better.
Congratulations, great work!!!
-
This is so Perfect. Thanks @rstoenescu for all the hard work.
-
Thank you so much for this excellent framework. I started a project with it a week ago using 0.14.9 and it took me a day to migrate to 0.15.1
0.14.9 was good
0.15.1 is even better !
It is so well organised and the new features are great.
I truly admire your work. Once I will have evangelised this framework at the place I work at, I will try to convince them to donate for sure.
Thanks again!! -
@Akaryatrh Thanks for the tip, I removed the local quasar-cli and reinstalled, now all is good. As you say, quite a change
-
@akaryatrh I noticed that quasar is not in package.json anymore as well (just the cli). How does this work, since I used to simply delete my node_modules folder and run
npm ionce in a while, but this no longer possible I suppose? -
@MusicForMellons I don’t know why you have to delete your
node_modulesfolder periodically, but whilequasar-cliis referenced on thepackage.jsonfile, when you do anpm i, It should be installed back.BTW, as stated in the documentation :
Quasar CLI is installed both globally and locally. When you issue a Quasar command, the global installation defers to the project locally installed Quasar CLI
-
@Akaryatrh Yeah, that’s clear. But then you not have the quasar framework as that needs
quasar init, right? So that’s my point/ problem.BTW, I do not seem to be the only one deleting node_modules to make a fresh start, e.g. see current quasar docs:
http://quasar-framework.org/guide/quasar-upgrade-guide.html#Starter-Kit
‘Sometimes after you npm install a package, or even update current packages, NPM might screw things up. You’ll get errors that some packages are missing and you need to install them. In such cases, delete node_modules and package-lock.json and npm install again.’ -
@Akaryatrh You’re right. I tested deleting both node_modules and package-lock.json and then
npm iand then I can runquasar devlike before and it works. So apparently install of quasar, vue, vuex, etc is all ‘taken care of’ via quasar-cli in package.json (I do not think this used to be the case). -
excellent work. thank you
-
excellent work. thank you
-
This is groundbreaking work. I’m totally in awe. I’m impressed, I’m surprised and I’m… just happy! Thanks!
-
This is so cool, I’m really impressed so far. Great work. Thank you<3
-
I’m a bit confused with he back button post. Could you provide us with an example of how we should implement back button into our layout when stack or a demo on how to do this? Thanks!
-
@aznric3boi91 Yeah, not sure what the modal code relates. Though I think he’s saying you can’t implement it?
