-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Get rid of rimraf #114
Labels
cleanup
Housekeeping
Comments
Actually I'll first test if the hacks are still required. |
They aren't :) Looks like browserify is smart enough to respect the |
This was referenced Jan 6, 2018
@vweevers So we can just remove the |
No, because of #116 (comment) |
vweevers
added a commit
that referenced
this issue
Mar 29, 2019
Done in #174 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This was added in 001c86e, excluded from browser builds in 80822a7 and necessary because
abstract-leveldown/testCommon.js
requiresrimraf
.I think we should solve this in
abstract-leveldown
so that memdown (and others) don't need these hacks. I'll open an issue. /cc @ralphtheninjaThe text was updated successfully, but these errors were encountered: