Oh I understand the purpose. And I'm sorry if I didn't explain myself properly but I do not plan to have a centralized node_modules folder. I am still going to have one node_modules folder per project. I simply did not want to have it inside the same SVN repo because it makes the repo weigh 100mb instead of 2mb, and it makes commits and deployments much longer than they need to be. Since the node_modules folder doesn't change or hardly ever changes, I prefer to isolate it and have it be in its own SVN repo.
But that's just me and how I segment my projects into multiple repos. Maybe it's not the best practice but it's how I learned to work when working as a small to medium team of developers and it's worked well so far. Def. thanks for the feedback though I appreciate the intention On Monday, November 18, 2013 2:31:42 PM UTC-5, ryandesign wrote: > > > On Nov 18, 2013, at 03:57, vesper8 wrote: > > > I plan to use SVN and wanted to segment the existing project into many > smaller repos to lessen the chance of conflicts when being working on by > multiple people. > > > > One thing I want to do is move the node_modules out of the main > application repo because it causes commits and deployments to take waaay > too long because of how massive the node_modules folder is. > > The node_modules directory should be in the same directory that contains > your package.json file. > > > I understand that the node_modules can be anywhere above the application > root so right now I've set it up so it looks like this: > > > > Before: > > /var/myProjects/ProjectX/node_modules/ > > /var/myProjects/ProjectX/app.js > > /var/myProjects/ProjectX/everything else > > > > After: > > /var/myProjects/node_modules/ > > /var/myProjects/ProjectX/app.js > > /var/myProjects/ProjectX/everything else > > The purpose of having a node_modules folder in each project is so that > each project can independently manage its own dependencies. > > Imagine ProjectX uses express 2.x, and so does ProjectY. So > ProjectX/node_modules contains express 2.x and so does > ProjectY/node_modules. Now you plan to move to a centralized node_modules > folder. What happens when you want to upgrade to express 3.x, which > necessitates changes to your project’s code? Are you prepared to make those > changes to all of your projects simultaneously? > > -- -- 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.
