Vue.js with Vuex / Flux Series

+1 for this

+1

+1

+1

I remain unconvinced that Flux is a desirable approach.

Maybe they want to know more about how to have more control on state when working on sites that use many components and have many developers working on them. If state or actions on the state will be all over the place, then you could imagine that switches will be all over the code. Like: User pressed a button which should add 1 to a counter, but 2 get added. Happy hunting in my muddy mystical swamp, kid! Hopefully you will spot that it's somewhere at somestuff.js, following some nested include called something.js @everybody vue-freeze is a mini one man git repository which I use to move all switches and switchers out of my warm swamp.

With the eventing system going the way of the dodo, I'd love to see how to best deal with managing state across components.

+1 to a serie to learn how to create single page applications with vue

+1 Personally desirable or not, it needs to happen. Too many people are waiting on this and it's simply the next step to take when learning Vue for pretty obvious reasons.

@stephan-v Yeah i also think so.

It's the next step "for obvious reasons"? What does that mean?

Who decided that it's the next step?

@JeffreyWay Evan You did because he went in this direction? And with "for obvious reasons" I mean because people are running into a brick wall because they are still stuck on using eventing, therefore going into a hell of dispatches and broadcasts being send back and forth.

Vuex is still in development but with 2.0 on the way broadcast and dispatch will be removed and Evan You's suggestion is moving to Vuex or using the global event bus. I really appreciate all the lessons but they will soon be a bit outdated because of major updates with 2.0 and I think it would be useful to learn Vuex for a lot of people.

I don't really see what the problem is here and why you are so hesitant to use(or create lessons) on Vuex but I would love to know. Love the rest of the Vue series.

Cheers.

I would appreciate a Vue SPA, Vuex and Laravel as a backend series. Sounds like an awesome combo :) I have done some minor SPA in mithril.js (collage course) and just started learning vue (thats how i found laracasts). Right now I struggle a bit in moving from minor SPA to bigger SPA and I think that in part it is becouse of my lack of knowledge and experience in arcitecture and state management. Right now my state and business logic is all over the place, litteraly ;)

+1 for vuex

+1

Perhaps you could expand on that @JeffreyWay . We've all heard the benefits of a uni-directional approach to app structure, I'd like to hear what you think are the downsides.

+1+1+1+1+1+1+1+

+1 :)

+1 :-)

+1

+1 : Single page website with Laravel as Backend :)

It would be better if master @jeffreyway have a explanation lessons how vuejs used in laravel spark and in this website

This is exactly where I'm stuck at the moment, so yet another +1 for me.

+100

I'd like to See VueJS + Router + webpack, + Store in data management

I believe Laravel Community is lack of motivation to do SPA, because Laravel already created a very beautiful blade engine for view layer, until now the community tends to use library (Pjax, etc) just to assist Laravel's View blade engine to achieve SPA.

But Laravel is back-end oriented. This leaves Laravel far less advantageous in front-end SPA.

This has to be left to VueJS those built-for-SPA front-end library to do the job. The cost of throwing Laravel view away to embrace full VueJS router SPA is relatively too high.

Disclaimer: I launched full-laravel 5.2 platform with aid of VueJS in frontend. Now I find out it is far more powerful to use VueJS SPA set with Laravel backend and Lumen as API. The UX and performance increase is INSANE!

Vuex is great tool for small spa. But become quickly a mess has your app grow. So much redondant code for each resources. especialy the Actions.

Everyone is looking at SPA but you have to look at it as a multi spa because if you use roles of some kind each will have different needs, just split up the code properly with webpack and build a SPA x role with reusable components. I can full understand Jeffry, laravel is a php framework and vue is a great tool to improve parts of the workflow, but if you build the front all in js the skills of the average developer now are not only the full understanding of laravel but also js witch is not an easy learning curve to get it right.

thx to those who commented here. useful reading. have been struggling myself with the need for virtually everything i'm doing to have an SPA look and feel. just about work project I have is moving more towards SPA approach. Haven't figured out whether PJAX is enough vs laravel back-end/api and VueJs+Vue-resource+Vue-router for user SPA experience.

broadcast & dispatch are gone from VueJs 2.0! It's time for vuex.

+1 for vuex series.

Vuex would be awesome.