-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: lazy load js-ipfs-http-client and async iterator support #8
Conversation
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.
@lidel this LGTM. Although it is a breaking change, I think we could actually merge it right ahead.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
5eeaa4d
to
99807d9
Compare
5d4f4e7
to
e4d7144
Compare
- remove external dependency - support window.IpfsHttpClient - remove defaultApiAddress (simplifies api) License: MIT Signed-off-by: Marcin Rataj <[email protected]>
- Renamed functions responsible for loading respective modules to more meaningful ones. - Updated examples/browser-browserify - Removed info about support for dynamic imports (JS modules) until we have a working example License: MIT Signed-off-by: Marcin Rataj <[email protected]>
0cafb99
to
3785592
Compare
BREAKING CHANGE: this switched ipfs-provider to the new JS APIs based on async iterators. More details in: https://blog.ipfs.io/2020-02-01-async-await-refactor/ License: MIT Signed-off-by: Marcin Rataj <[email protected]>
3785592
to
7901704
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.
The code LGTM! Tests seem to pass and I like the changes. Let's 1.0!
but it may impact your use cases, as you created #19 recently.
I prefer it this way where you can bring your own ipfs-http-client. Unless the constructor changes dramatically, this won't need to be updated in order for other stuff that depends on it to get updated, which is awesome.
@lidel Thanks for the new build. Integrated and tested on my side. Lazy load without the internal dependency is working as suggested. Great |
This PR:
js-ipfs-http-client
from the default bundle,(enabling people to lazily load it only when it is actually needed)
https://blog.ipfs.io/2020-02-01-async-await-refactor/
README
and code in./examples
iso-url
)First two are breaking changes, so I plan to release as v1.0.0.
We need this for unblocking some collabs, such as kiwix-js.