Open colinbrogan opened 2 years ago
Different things are definitely using different versions. :/ (I'm not very smart with the docker/etc. stuff, help?)
I did publish a new version to NPM recently 0.2020.1238
so hopefully Heroku will now use that?
People also keep talking about "git tag" and I also get very confused with that - how do I delete or deprecate it so it doesn't get loaded or used?
I had problems with user graph data syncing between browsers on the heroku 1-clicker. After some investigation, I discovered that the same problem occured when cloning the master branch, and either doing a local docker build, or an npm install from the github source.
In contrast to all of this, if I just ran npm install gun on a seperate folder, and started it from within the node_modules folder, the problem went away, and everything behaved as it should.
Here is the test code:
So, the following two approaches for creating the server have problems:
When you open the above html file in 2 browsers, you can see that only the location of the user logged into a given browser tab is logged to console.
Now, if you start a completely new folder and pull from npm:
When you open the html example again in two browser tabs, then both user locations are shown on each tab. This is correct.
Finally, if I then check the version that NPM brought in for me of gun, it outputs:
0.2020.1237
When I looked at the tag of the github master branch, it was set to 0.2019.plus-other-stuff. It appears that the github repo is out of date with your npm package. This wouldn't matter so much, except for the heroku 1-clicker. If you had this version in the github repo as a tag, then I could use heroku to generate a functional relay server for myself.