npm: what does UNMET DEPENDENCY mean?

876 views
Skip to first unread message

Rambo

unread,
May 25, 2011, 10:40:19 AM5/25/11
to nod...@googlegroups.com
Sorry about this silly question but i cannot find an explanation for that. 
I have my own modules in node_modules folder and when i execute "npm ls" those packages are listed as UNMET DEPENDENCY, but those modules don't depend on anything, they are just modules as folders with an index.js file.
Do I need to create a package.json with some dependency info so "npm ls" lists everything as normal?
This brings up another question. If my own module depends on another module that is already installed and resides in the same node_modules directory as my module, do I need to install it inside my module again? is it cleaner that way or it's not necessary? Notice that my module is project-specific and won't be re-used.
Thanks.

Isaac Schlueter

unread,
May 25, 2011, 11:58:50 AM5/25/11
to nod...@googlegroups.com
Please send a gist of the actual output to the np...@googlegroups.com
list. There's a package.json somewhere requiring something that isn't
the right version, or there's a bug in npm ls. Either way, need to
see the actual output.

> --
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com.
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en.
>

Reply all
Reply to author
Forward
0 new messages