20.12.2013, 03:48, "Mikeal Rogers" <[email protected]>:
this is actually why we checkin our deps. we'll fix a module and deploy that fix before the maintainer has accepted it. we don't really see fixes that don't go back in to projects, working with open source maintainers is part of the culture.On Dec 19, 2013, at 3:21PM, Alex Kocharin <[email protected]> wrote:It resulted in huge node_modules folder checked in (with binary deps because nobody cared), they weren't updated at all (and were outdated for like a year).this just requires some diligence and using dedupe often.And the worst thing is that when people find bugs in modules, they actually commit their change directly to node_modules!
I just got a bit of an issue with that.
Suppose you do have a certain fix that isn't going to make it to upstream any time soon. For example, it's too specific for your case, or for whatever else reason.
How do you update this module in the future? You can't just do npm update, because it'll remove your changes, right?
--
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
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
