browserify-fs
browserify-fs copied to clipboard
fix: π Updated levelup version to 4.2.0 fixing audit
Closes: #20
@mafintosh please merge this and create an updated release
I would like to request for a change, if that's okay. There is another vulnerability in levelup
. the problem had been fixed already form their side https://github.com/Level/levelup/issues/676. However, I'm not sure if it will be a patch/minor version bump. if not, then we need to update this package.json as well.
refer to this picture for the vulnerabilities that I had faced using rollup
plugin.

@srepollock This PR is incomplete. There have been breaking changes between levelup 0.x and 4 you'll need to account for.
@mafintosh, have you had a chance to look at this yet? It would help us out a lot if this were fixed.
I donβt have any time to review this. If someone wants to take it over let me know.
@mafintosh user @lcsvcn has approved this and I addressed the issues @Vehmloewff commented on. Is there any more reason stopping this from being merged in?
I apologize and would like to update this thread for the sake of @trevorblades . I have accidentally deleted the GitHub repo referenced in the PR here. I have recreated the repo and made the necessary changes here. I will have a release set up as well to pull from NPM, but I would suggest that this PR get some movement.
If because I deleted the repo there is no way to merge in this PR, please @ me here and I can submit a new one with the new repo. Cheers
@srepollock github maintains the code changes of deleted repos, thankfully. In the past it would've auto closed this PR but no more.
Thanks for restoring that repo @srepollock!
Any updates?
Could someone teach me how to use @srepollock's fixed version of the repo instead of this version? Seeing that this PR will not be merged anytime soon.
@SamsonChoo npm i srepollock-browserify-fs
https://www.npmjs.com/package/srepollock-browserify-fs
Hi this appears to still be an open issue. Is there a way to move this along and get it resolved? Happy to help in anyway I can
@penfold45 currently the solution is to fork and fix yourself or to use someone else's fix. The developer seems to be inactive on here at this time.