-
-
Notifications
You must be signed in to change notification settings - Fork 449
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
Dat v14 -- breaking changes #1173
Conversation
Reflects dat-ecosystem-archive/design@7f024ea , which removed dat-data-logo.png
15eb81f
to
f716675
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I'll update the SDK to use hyperswarm too at some point in the near future. 💜
Got myself a fresh copy of node v12.16.1 and tried to https://gist.github.com/decentral1se/8e45d5527c30414a8d2793b6e6a2999c If I could get past this it'd be cool to test because I was struggling to get connectivity sorted from my homebrew here in the house. Thanks for the good work! |
@decentral1se ah looks like it's still trying to install discovery-swarm. can you rm -rf node_modules and rm package-lock.json, and then reinstall? |
Unfortunately, I still explode into flames: https://gist.github.com/decentral1se/90322a42bb8112239a64dedf7edc1e7d. Not sure what I'm doing TBH :) |
@decentral1se Oh I figured it out, dat-doctor is installing discovery-swarm. |
okay @decentral1se this should be ready for testing now, my apologies |
Yep that installs! I could share some test folders! It's a bit hard to test with friends who can't go through this installation procedure to check if we can share what was problematic to share before. Also the dat doctor is gone now, so I can't check if those issues are resolved (was seeing a "cannot find public ip / port" message) :) If this could go out on a new release of dat-desktop, I'd definitely be able to give it more testing. |
Installs and passes test over here. 🎉 (If you'd like any help testing something, please let me know. I've been meaning to spend more time checking out this stack.) |
The network of dat v14 will not be compatible with earlier versions of dat. The .dat metadata file will still work, but older clients should upgrade to v14.
It will have big improvements:
dat share
command. Now,dat share
anddat sync
do the same thing, so you no longer have to remember if your directory has a dat in it already.