Thanks for sharing ❤️ I had stack Vue with Node / Express. So when it comes to this i found feathersjs is cool because they had feathers-vuex, and it works out of the box.
since feathers are just combination of express and socket the syntax are not the problem.The problem is out-of-the-box feature. i must understand it before use, cause when it comes to customization it could be headache 😂
like to setup my own project so it can stay simple.
If "out-of-the-box" is good documented and you know what you are using it shouldn't be a problem anymore, but I totally get your point. When you have a look at the roadmap, "extensions/modifications" are the next big feature for Crana: Then you will be able to extend/modify every single aspect of Crana (this means that React will be made optional and extension for every library/framework etc can be created quiete easily). This has the big advantage that nothing is redundant and you have a "single source of thruth" for configuration files (etc.) for all your projects. So when you find a bug in e.g. the webpack config, you fix it once for all your projects (and with extensions you will not loose flexibility).
Thanks for sharing ❤️ I had stack Vue with Node / Express. So when it comes to this i found feathersjs is cool because they had feathers-vuex, and it works out of the box.
since feathers are just combination of express and socket the syntax are not the problem.The problem is out-of-the-box feature. i must understand it before use, cause when it comes to customization it could be headache 😂
like to setup my own project so it can stay simple.
If "out-of-the-box" is good documented and you know what you are using it shouldn't be a problem anymore, but I totally get your point. When you have a look at the roadmap, "extensions/modifications" are the next big feature for Crana: Then you will be able to extend/modify every single aspect of Crana (this means that React will be made optional and extension for every library/framework etc can be created quiete easily). This has the big advantage that nothing is redundant and you have a "single source of thruth" for configuration files (etc.) for all your projects. So when you find a bug in e.g. the webpack config, you fix it once for all your projects (and with extensions you will not loose flexibility).
Yeah thats it, and i actualy look at the roadmap first then comment here. haha.
I would love to fork and maybe make another template for the client. Its insteresting.