-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
unmet dependencies #82
Comments
I had to deal with that as well, and solved it in the webpack configuration by ignoring this import. You may want to do the same in your browserify configuration. You may also want file an issue to their repository, as I think they shouldn't do what they do, or at least the way they do it. |
@n1k0 Tnks for the hint on this. Shouldn't this note be on some README.md section (i.e. Troubleshooting)? |
For people that use browserify the solution is to use the var bundler = browserify({ ... yourconfig ... }).ignore('buffertools') |
You're most definitely right. I'm also considering switching to another similarily scoped lib, but can't find anything as tiny as "deeper"; eg. switching to lodash |
Yes, that would be the best approach. In the meanwhile, we should add the README.md. I will PR that for you. |
That's awesome, thanks. On my end I have an idea to solve the problem in the deeper lib itself as described in othiym23/node-deeper#3 (comment); gonna work on a PR. |
Thanks for the ".ignore('buffertools')" tip! I was completely stuck on this one and that fixed it! |
There is some issue with
deeper
dependencybuffertools
. I get the following error message when trying to browserify:Therefore I can't get the JS bundle.
The text was updated successfully, but these errors were encountered: