-
Notifications
You must be signed in to change notification settings - Fork 57
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
Nuxt 3 Vuex workaround #44
Comments
What's their new plan? |
I asked a question here: |
lol you have to enabling plugins in
is to make it nice and clean, obviously heh
go through the link above |
OK, so as long as the plugin's |
@chiboreache - did you have any more info on this? Is this still an issue I need to handle? |
@davestewart I just got bogged down in routine (and python), sorru =) but I'm finally back, and I already tired from getters and mappers, so yeah, I will dig in at this week 💯 |
I know the feeling! (of getting bogged down) |
but there is an error in 2.4 version (with 1.4 from example project all fine) so yeah, that wasn't hard, heh: import pathify from 'vuex-pathify'
import hello from './modules/hello'
console.log('STORE FILE LOADED!')
export const plugins = [ pathify.plugin ]
export const modules = { hello }
export const actions = {
nuxtServerInit(context, value) {
console.log('NUXT_SERVER_INIT!')
}
} this is thrue Module mode index.js ;) I can pr you fully loaded coffeescript variant, just a little bit later =) |
So what was the final conclusion? Does Pathify need updates to code or docs? |
Yeah, of course it would be nice, since Nuxt going that(modules) way. When I finally figuring out how to PR properly, I will push you coffee example ;) |
is this being used with NUXT? as of today. new NUXT with vue 3 is releasing today... |
Not sure. I'll reopen the issue... |
Hi!
Since Nuxt 2 already warning us about deprecating classic way of doing Vuex, so my question is:
how to make neat
store.set('foo/bar')
work againwithout
import store from './store/index'
?The text was updated successfully, but these errors were encountered: