search

davidbanham / field-marshal

A landlubbing rear-admiral
BSD 3-Clause "New" or "Revised" License
27 stars 3 forks source link

npm interferes with itself #4

Closed davidbanham closed 10 years ago

davidbanham commented 10 years ago

Currently if we're running two instances of the same repo on one machine, they run in the same directory. This is fine most of the time.

It's not fine, though, when you're trying to set up two instances of the same repo with npm at the same time. npm freaks out about not being able to get the locks it wants and nobody is happy. This will probably be the case more generally, too.

What I propose is that each process instance runs in it's own directory. This will require a git checkout for each process spawn, but I think that's fine.

davidbanham commented 10 years ago

I fixed this months ago and forgot to close the issue.