it is not a good practice, it's just was the only way to ensure the deps to be stable, because npm allowed to override package versions with publish --force which then made shrinkwrap a bit useless so far. this may change soon (cant find the post which announce it, but it is announced). but so far it is a required practice. to solve the issue with native extensions: npm rebuild rebuilds all them on current thing. you can setup this as post-install hook in your deployment process.
this thing with line breaks this article might help https://help.github.com/articles/dealing-with-line-endings#platform-all Am Mittwoch, 19. Februar 2014 10:02:28 UTC+1 schrieb Donald Pipowitch: > > Hi, > > I know it is good practice to commit node_modules/ if you develop an app. > But our developers use Windows, Linux and Mac and some node_modules/ seem > to generate platform-specific code and it seems some of our developers hat > problems with git saying, that line-breaks would have changed, even it no > file was changed. Has somebody else encountered these problems? How do you > solved it? We think we will use a private/mirrored npm in the future with > specific locked versions for each mode (with npm shrinkwrap). > > What do you say? > > Thanks, > Pipo > -- -- 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.
