You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I came across the proxyquire issue you opened, and it's the exact problem we face. I have tried out your fork, and it definitely seems to fix the memory leak, but I'm seeing other issues, like with stubs leaking into other proxyquire calls that are not stubbing a built-in module.
You made mention of building a different stubbing solution for your project. Did you open source/publish this? Very interested.
The text was updated successfully, but these errors were encountered:
This code is what we used for our project. If I recall correctly, we were using this dependency in package.json by referencing the git url to this repo.
Hello.
I came across the
proxyquire
issue you opened, and it's the exact problem we face. I have tried out your fork, and it definitely seems to fix the memory leak, but I'm seeing other issues, like with stubs leaking into other proxyquire calls that are not stubbing a built-in module.You made mention of building a different stubbing solution for your project. Did you open source/publish this? Very interested.
The text was updated successfully, but these errors were encountered: