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

Use is-buffer module to check for buffers, avoiding browserify bloat #3

Closed

Conversation

andyburke
Copy link

No description provided.

If we check for Buffer at runtime, browserify won't pull in its core buffer implementation, saving ~40K or so.
Check Buffer at runtime to avoid browserify shims
@williamkapke
Copy link
Collaborator

Hmm.. yes I want to avoid this- however I don't want to introduce a sub-dependency (it's a legal thing for many)

The guts of is-buffer is tiny so I'd like to just add it directly with attribution to @feross for his work.

@feross, if you object- please let me know and I'll consider other options.

@feross
Copy link

feross commented Mar 6, 2015

@williamkapke The code is MIT licensed, so there shouldn't be any legal issues with using the module directly. But I don't mind the way you've used it directly either :)

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

Successfully merging this pull request may close these issues.

3 participants