Are there any plans to port vuex-pathify to vue3 or is this project becoming abandonware? Thanks.

[iknowmagic]

Inquiring about vuex-pathify being ported to vue3

[davestewart]

Ouch! That hurts 😆

Well, the codebase has been stable on Vue 2 so I simply haven't needed to make any updates for a long while.

As for Vue 3, I would need to a) know what best practices are and b) look into the state of Vuex in Vue 3.

Are these things pretty much settled now?

Maybe you can help with some answers and I can look to see what I can do.

[iknowmagic]

Thanks.

vuex-pathify was sort of working with Vuex 4; the "get" component helper did not work but the "sync" helper did work. Now Vuex is throwing all sorts of errors when used with vuex-pathify. See the attached screenshot for an example.

As it is, it looks like vuex-pathify is not usable with Vuex 4 (Vue 3).

[NGPixel]

I also started to use Vue 3 for a new project and found out that vuex-pathify doesn't work.

The main issues seem to be:

• dependency on vue-class-component, which doesn't work in Vue 3 and cause warnings during build
• Some error thrown at runtime as noted by @iknowmagic

Hopefully this library can be updated to work with Vue 3 as it makes working with vuex so much easier!

[davestewart]

OK, good info; thanks both.

I'm currently deep into another project and finding it very hard to find the time and brainpower to switch to anything else, but I get that the more time goes by, the more chance you guys will have of jumping ship, so I'll make this a priority.

Sorry it's been so long since I checked in on GitHub as well; that should give you an idea of where my focus is right now!

[bkarlson]

It seems like Vue 3 is not supported by vue-class-component yet, their README is confusing. Gotta wait a bit more I guess..
https://yarnpkg.com/package/vue-class-component

[MajesticPotatoe]

Oddly enough, I've been experimenting with vuex-pathify on vue3 + vite and managed to get it working. Had to force vuex-pathify to use vue-class-component v8.0.0-beta.2, and had to borrow some stuff from #95 to get it working in setup(). Haven't run into any of the errors mentioned about with get or sync, and the one VCC error was solved with the beta.2, so looks promising.

[iknowmagic]

How about using adjusting vuex-pathify to work with vue 3.1+, since vue 3.1+ is supposed to be fully backward-compatible with vue 2 ?

[davestewart]

Sorry everyone; I've not been good to my word and haven't worked on this yet.

Can someone set up a sample project and post the repo link?

As soon as that is done, I will work on this.

Thanks.

[NGPixel]

I made a fork of the project without the vue-class-component dependency. This fixes all the warnings when using Vue 3. Also replaced rollup with esbuild for the actual build as I was getting all sort of errors.

It has both the CommonJS and ESM versions.

# Using npm:
npm install @requarks/vuex-pathify

# Using yarn:
yarn add @requarks/vuex-pathify

Hopefully we'll see an updated version from the maintainers in the future, but in the meantime this should address the issues raised for Vue 3.

[davestewart]

Hey @NGPixel - I'm happy to merge this if it does the job.

Do you want to make a PR for further discussion?

[iknowmagic]

@NGPixel Many thanks for the work :)
I installed your version and unfortunately, the types are missing; without types, it is breaking Vue 3 / Typescript.

[NGPixel]

@iknowmagic I added back the typings in 2.0.2 while removing the vue-class-components reference from them. However I'm not using Typescript so I have no idea if more changes are needed. Let me know...

@davestewart I can make a PR but my version basically just undo the vue-class-component PR. So anyone that relies on these decorators would see their project break. I don't have any experience with decorators so I wouldn't be the best person to propose a proper update to the library while keeping this functionality. I simply wanted a quick patch that removes the warnings caused by vue-class-components. So this is probably not what you want, unless you want to create a major version that removes that functionality altogether.

I also stripped much of the project (docs, demo, tests, etc.) to remove any rollup dependencies which were causing npm install errors (specifically node-sass which is deprecated anyway). Some work would need to be done on that front as well.

[davestewart]

@NGPixel - gotcha.

Well, thanks for sharing the info. The Vue 3 version will be a major version patch for sure.

Based on what @iknowmagic has mentioned, I may just rewrite it in TypeScript and kill two birds with one stone.

[iknowmagic]

Thank you so much @davestewart
@NGPixel the types from the current vuex-pathify version would not work out-of-the-box, unfortunately