NPM Depends "usage" issue from Modulus

[cfly15]

I am getting this error when I am deploying to Modulus, I see Npm depends in the package.js file but still getting the error.

Error: Can't find npm module 'usage'. Did you forget to call 'Npm.depends' in package.js within the 'meteorhacks:kadira-binary-deps' package?
at Object.Npm.require (/mnt/data/1/programs/server/boot.js:106:17)
at Package (packages/meteorhacks:kadira-binary-deps/index.js:2)
at /mnt/data/1/programs/server/packages/meteorhacks:kadira-binary-deps.js:22:4
at /mnt/data/1/programs/server/packages/meteorhacks:kadira-binary-deps.js:31:3
at /mnt/data/1/programs/server/boot.js:161:10
at Array.forEach (native)
at Function..each..forEach (/mnt/data/1/node_modules/underscore/underscore.js:79:11)
at /mnt/data/1/programs/server/boot.js:82:5

[arunoda]

I hope this is due to the Meteor 0.9 and modulus's demeteorizer is not supporting this. Let me give it a try.

[cfly15]

That's my hope too. @hellogerard just upgraded Differential.io to 0.9 and
didn't get this error. I am going to keep trying things but wanted to let
you know that I was getting the error

On Friday, August 29, 2014, Arunoda Susiripala notifications@github.com
wrote:

I hope this is due to the Meteor 0.9 and modulus's demeteorizer is not
supporting this. Let me give it a try.

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

Colin Flynn
Partner at Differential http://differential.io
Co-founder of The Canopi Agency http://thecanopiagency.com
513-549-2359, @colinpflynn
linkedin.com/in/cfly15

[arunoda]

see: XervoIO/demeteorizer#64

That's because Differential.io may not use any npm specific packages. Not sure BTW: Best bet is to stay for 0.8.3 for couple of days.
kadira is backward compatible with 0.8.3 and we are pushing new releases for old atmosphere/mrt as well.

[cfly15]

Got it. Thanks! Have a good weekend

On Friday, August 29, 2014, Arunoda Susiripala notifications@github.com
wrote:

see: XervoIO/demeteorizer#64
XervoIO/demeteorizer#64

That's because Differential.io may not use any npm specific packages. Not
sure BTW: Best bet is to stay for 0.8.3 for couple of days.
kadira is backward compatible with 0.8.3 and we are pushing new releases
for old atmosphere/mrt as well.

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

Colin Flynn
Partner at Differential http://differential.io
Co-founder of The Canopi Agency http://thecanopiagency.com
513-549-2359, @colinpflynn
linkedin.com/in/cfly15

[arunoda]

you too :)

[jhgaylor]

I experienced this issue as well and tried tons of tricks to get it to work, but it never did. If I remove Kadira from my project the deploy runs smoothly. I'm not sure if the problem is in Kadira or one of the onmodulus components, but I can't wait til I can add Kadira back to my project. It's a very important tool to me.

[arunoda]

Hi it's a modulus issue. They fix it afaik. Now all are okay right?

And we also have an issue on ourside too. We fixed that too.

[jhgaylor]

Sounds good. I'm following the appropriate issues to stay informed. I can't wait to get kadira added back :) Thanks.

[arunoda]

awesome. Try simply updating kadira and both modulus npm module. I hope
that should work.
Ping me, if that's not.

---

Arunoda Susiripala

@arunoda http://twitter.com/arunoda
http://gplus.to/arunodahttps://github.com/arunoda
http://www.linkedin.com/in/arunoda

On Sun, Sep 14, 2014 at 5:53 AM, Jake Gaylor notifications@github.com
wrote:

Sounds good. I'm following the appropriate issues to stay informed. I
can't wait to get kadira added back :) Thanks.

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

[jhgaylor]

According to a comment by scald on this issue XervoIO/demeteorizer#64 removing the package, deploying, adding the package, and finally redeploying would fix the issue. It worked for me.

[arunoda]

Great. Thanks for sharing it here :)

---

Arunoda Susiripala

@arunoda http://twitter.com/arunoda
http://gplus.to/arunodahttps://github.com/arunoda
http://www.linkedin.com/in/arunoda

On Sun, Sep 14, 2014 at 6:53 AM, Jake Gaylor notifications@github.com
wrote:

According to a comment by scald on this issue XervoIO/demeteorizer#64
XervoIO/demeteorizer#64 removing the
package, deploying, adding the package, and finally redeploying would fix
the issue. It worked for me.

—
Reply to this email directly or view it on GitHub
#1 (comment)
.