Skip to content
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

ported to modern feathers scaffold and Feathers 3 #8

Open
httpete opened this issue Feb 28, 2018 · 3 comments
Open

ported to modern feathers scaffold and Feathers 3 #8

httpete opened this issue Feb 28, 2018 · 3 comments

Comments

@httpete
Copy link

httpete commented Feb 28, 2018

Hi,

I have spent the last two days learning from your example which has a good starting point but is outdated. I think I have it working on the latest feathersjs. Can we collaborate on this somehow so others don't have to do this? A Vue/Vuex/Feathersjs is a killer combo.

@L-K-Mist
Copy link

L-K-Mist commented Mar 4, 2018

I'm in the same place you were httpete, still working through it myself. Besides updating the imports to '@feathersjs' format, what other gotcha's did you encounter?

@httpete
Copy link
Author

httpete commented Mar 4, 2018 via email

@httpete
Copy link
Author

httpete commented Mar 11, 2018

I am struggling with babel and all with vue, getting confusing results in the chrome debugger. I think we should abandon the babel pipeline, and use TypeScript, class based vue components. There must be a good boilerplate TypeScript Vue project we can just pop on top of the fine featherjs integration you have.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants