Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

docs: browserify-zlib-next begone! #882

Merged
merged 1 commit into from
Jun 16, 2017
Merged

Conversation

daviddias
Copy link
Member

closes #758

@daviddias daviddias added the status/in-progress In progress label Jun 16, 2017
@daviddias daviddias merged commit de46cee into master Jun 16, 2017
@daviddias daviddias deleted the no-more-browserify-zlib-next branch June 16, 2017 18:31
@daviddias daviddias removed the status/in-progress In progress label Jun 16, 2017
@victorb
Copy link
Member

victorb commented Jun 17, 2017

I think this was a bit premature as the PRs to update zlib in webpack and browserify have yet to be merged.

PRs to watch for progress:

@daviddias
Copy link
Member Author

It will work for WebPack due to semver, not to browserify, unfortunately.

That being said, users should not experience this as we now use multiplex by default, nevertheless, let's continue to push to get that updated in Browserify.

MicrowaveDev pushed a commit to galtproject/js-ipfs that referenced this pull request May 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Seeing a zlib error between browser nodes and node.js nodes?
2 participants