Skip to content
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

readable-browser.js does not export everything readable.js does #408

Closed
angelo-v opened this issue May 9, 2019 · 6 comments
Closed

readable-browser.js does not export everything readable.js does #408

angelo-v opened this issue May 9, 2019 · 6 comments

Comments

@angelo-v
Copy link
Contributor

angelo-v commented May 9, 2019

I am wondering, why readable-browser.js is missing some exports. E.g. readable.js is exporting finished and a library that I am using imports it. readable-browser.js does not export finished. Now my application breaks, because finished is undefined in a browser application.

Is this intentional? Am I using it wrong?

@angelo-v
Copy link
Contributor Author

angelo-v commented May 9, 2019

finished and pipeline got added to readable.js in this commit and it seams to me, that it just was forgotten to update readable-browser.js

@mcollina
Copy link
Member

Good spot! Would you like to send a PR?

@angelo-v
Copy link
Contributor Author

I could add those exports to readable-browser.js, yes. But what is the purpose to differ between readable-browser.js and readable.js in general? Is the separation still justified?

@mcollina
Copy link
Member

readable.js accesses the process.env object. readable-browser.js does not, and it will yield smaller bundles.
Overall, yes, they are justified and needed.

@angelo-v
Copy link
Contributor Author

Ok, I will prepare a PR

@angelo-v
Copy link
Contributor Author

fixed via #409

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants