-
Notifications
You must be signed in to change notification settings - Fork 302
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
io.js support? #197
Comments
Same issue. |
Same here. |
See my PR over there at thlorenz/proxyquire#52 @adam-lynch |
Thanks. On Sun, 1 Mar 2015 00:06 Sebastian Meyer [email protected] wrote:
|
proxyquire |
@adam-lynch could you please update the dependencies then? 😀 |
@bastimeyer will do today :) |
|
@adam-lynch @bastimeyer Awesome thanks guys! |
@adam-lynch thx.. also pls don't forget to bump the dependency version inside the grunt repo too... otherwise [email protected] will be resolved:
|
@bastimeyer won't it just work? (https://nodesource.com/blog/semver-tilde-and-caret). Correct me if I'm wrong. Or maybe you just mean I should bust the cache. |
current version is 1.1.0 though |
Thanks. Just published a new grunt version. Regards, On 6 March 2015 at 00:54, Sebastian Meyer [email protected] wrote:
|
Cool, thanks 👍 |
Hi, everything works OK in node 0.12, but in io.js 1.3 I get the error below. Looks like for some reason mdl in proxyquire is read-only. Does anybody have this working in io.js or is there an alternative to proxyquire?
I asked the same question on proxyquire here but no love so far: thlorenz/proxyquire#51
The error occurs here: https://github.com/thlorenz/proxyquire/blob/master/lib/proxyquire.js#L15
The text was updated successfully, but these errors were encountered: