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

Re-Integrate express-vue #69

Open
telion2 opened this issue Mar 6, 2018 · 2 comments
Open

Re-Integrate express-vue #69

telion2 opened this issue Mar 6, 2018 · 2 comments
Assignees
Labels
bug enhancement FutureFeature Feature to implement in the next iteration

Comments

@telion2
Copy link
Collaborator

telion2 commented Mar 6, 2018

One of our main packages has made a major update, which demands some code changes so that
the project can work with the new module again.
If we update this module we can finally use node-modules on our frontend like vuex which will make the whole datamanagement a lot easier in a lot of ways.

Read these 2 Issue before trying to migrate to prevent errors.
express-vue/express-vue#159
express-vue/express-vue#158

Also when working on this issue please switch to the 'testNewExpressVue' branch.

@telion2
Copy link
Collaborator Author

telion2 commented Mar 12, 2018

the issues of express-vue are solved. We can re-integrate the whole thing now.
This also means that #86 can be solved with the pako approach.

@telion2
Copy link
Collaborator Author

telion2 commented Mar 12, 2018

It seems a new bug appered making mixins unusable for now:
express-vue/express-vue#163

telion2 added a commit that referenced this issue Mar 12, 2018
sven-mayer pushed a commit that referenced this issue Mar 19, 2018
@telion2 telion2 added the FutureFeature Feature to implement in the next iteration label Apr 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug enhancement FutureFeature Feature to implement in the next iteration
Projects
None yet
Development

No branches or pull requests

1 participant