Home > Enterprise >  Several people on same project using different package manager?
Several people on same project using different package manager?

Time:10-28

Let's say we have a Vue/React project that requires 3 people, but each of those people has a different taste in package manager. The first person already feels cozy using npm, the second one uses yarn because he thinks it has better security, and the third person loves to use pnpm because he thinks it can save storage when having multiple projects. Is it possible if that one project that is being worked on by those 3 people to run on each person's device using their chosen package manager?

Even if it is possible, is it something that is normal? Or is it something that we should avoid?

CodePudding user response:

It is something that you should avoid. Even if they used the same lockfile, there would be slight differences in how they work, so people would get "works on my machine" issues. You don't want to spend your time figuring out such issues.

Each project needs to pick one package manager and stick to a given major version of that package manager. You can even go one step further and stick to a given exact version of that package manager. That will make your setup most stable. You can use the new packageManager field for that in package.json:

{
  "packageManager": "<package manager name>@<version>"
}

But you need to enable corepack as it is an experimental feature of Node.js for now:

corepack enable
  • Related