Closed raphael10-collab closed 3 years ago
I haven't tried integrating hypermerge and vue, so I'm glad to see someone working on it. I suspect the issues are coming from directly including sodium-native, which I bet has had its interface changed since we last imported it to hypermerge.
You might want to look at pushpin, or github.com/pvh/needle, which already has all the electron bits hooked up, and just strip the React front-end out and replace it with vue.
@pvh does it mean that it would be better to remove sodium-native from the packages installed?
I will definetely have a look at pushpin and needle in order to understand how to, step by step, use hypermerge with vue.js and electron.js
sodium-native should already be included transitively as part of the hypermerge package dependencies and shouldn't require manual installation at the electron app level (see, for example: https://github.com/automerge/pushpin/blob/master/package.json).
Thank you Peter
BTW, feel free to ping me on the automerge slack -- would be happy to have a synchronous conversation about what you're trying to do and while I probably can't troubleshoot all your problems I'm quite willing to discuss your overall plan and tell you about the various bits we've already overcome.
I'm trying to make the chat example working in an electron.js app I'm developing.
The chat example within the hypermerge folder works fine:
But with the electron.js app I'm developing I get these errors:
This is the complete package.json :
I imported all hymerge types in /src/types:
(base) marco@pc01:~/webMatters/electronMatters/GGC-Electron$ vue info
I discovered that these error disappear one by one if I put in /src folder of my electron.js app all these files: https://github.com/automerge/hypermerge/tree/master/src
But all these files are indeed already present in node_modules/hypermerge/src folder :
So.. why I get for example this error:
?
How to solve the problem?