only option is to install all dependencies, then remove all
sub-dependencies and reinstall then manually also.
but why do you that that anyway?
Am Dienstag, 23. Oktober 2012 01:22:47 UTC+2 schrieb Alex Kocharin:
>
> Hi all,
>
> Some node.js modules depend on strict versions of another modules like
> that:
> "dependencies":{"mongodb":"0.9.9-3"} // mongode
>
> or that:
> "engines": { "node": "~0.6" } // express did it some time ago
>
> Now suppose I want to always use newer versions of any modules and don't
> care much about what maintainers thinks about it. What should I do?
>
> Is there any option for npm to lose respect for upper bounds of version
> range, but still respect lower bounds? Or any configuration like "whenever
> you see module@X, always install module@Y"?
>
> --
> // alex
>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
