-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Vuex #47
Comments
Hello @strixy
I changed my mind, adding different versions of the template soon: Have a great day! |
Thank you for agreeing to add Vuex. It appears in the official Vue documentation as the only alternative to DIY state management. Good idea to mention Babel. Come to think of it, don't you have Vueify already included as well? You should maybe mention that in the docs. That's a big win too. When you say "Vuex not for everybody", what other options are there besides creating your own? I'm curious, is there a cool toy I haven't played with yet? |
May I mention two JavaScript database here,
I think both are very popular database for now. I used LokiJS in my project, with IndexedDb adapter (there's a file adapter also.) When use lokijs, there is a gotcha when build with webpack ( node: {
fs: "empty"
} There also someone mentioned config like "target": {
"anyOf": [
{
"enum": [
"web",
"webworker",
"node",
"async-node",
"node-webkit",
"atom",
"electron",
"electron-main",
"electron-renderer"
]
}, Will try to use |
Thank you! |
cordova-template-framework7-vue-vuex-babel-webpack +1 |
1 similar comment
cordova-template-framework7-vue-vuex-babel-webpack +1 |
I created a new release that is using Vuex and babel features :) you can check on (2.0.3): |
Any interest in adding Vuex as well? I've used your project here twice and I like it. I look forward to using it more.
I find that adding Vuex is almost always my next step and even when it's not, it's only because I'm rolling my own for very small testing projects. In those cases, I would be just as happy to have Vuex already installed.
This is just a suggestion. You might have other plans or use cases to meet and if so, no worries at all.
I hate having to post this as an issue. Is there a better way to have this conversation? I'm relatively new to Github still.
Thank you for your efforts on this project already. Greatly appreciated.
The text was updated successfully, but these errors were encountered: