Support custom packageManager other than npm/yarn/pnpm.

[zyy7259]

What problem does this feature solve?

Currently the --packageManager only supports npm/yarn/pnpm.

This feature will let the end user specify a custom node package manager.

The company I worked at uses a private packageManager. Right now I cannot find a way to use it with vue-cli to create my project.

What does the proposed API look like?

--packageManager xxx

[zyy7259]

happy to send a PR

[Alex-Sokolov]

It would also be nice to be able to configure per-project package manager via vue.config.js. For example, you usually use yarn everywhere, but sometimes you support projects where npm is used. And you don't want to delete yarn.lock and reinstall node_modules to avoid side-effects because of the different folders structure

[LinusBorg]

@zyy7259 how would you tackle the possibly different commands that some custom package manager might have? These would have to be mapped somehow, i.e. what command is the qeuivalent of "npm install"?

[haoqunjiang]

@Alex-Sokolov in v4 we've refactored the package manager related stuff and it now infers the project manager from project lockfiles

vue-cli/packages/@vue/cli/lib/util/ProjectPackageManager.js

Lines 70 to 76 in 91024a7

	if (forcePackageManager) {
	this.bin = forcePackageManager
	} else if (context) {
	this.bin = hasProjectYarn(context) ? 'yarn' : hasProjectPnpm(context) ? 'pnpm' : 'npm'
	} else {
	this.bin = loadOptions().packageManager || (hasYarn() ? 'yarn' : hasPnpm3OrLater() ? 'pnpm' : 'npm')
	}

[haoqunjiang]

If the subcommands are identical to npm, just use command-line alias (like, alias npm="tnpm".

If not, it will surely increase our maintenance burden. We are not going to support custom package managers without a clear plan of future maintenance.

[zyy7259]

alias won't work with execa sindresorhus/execa#100

[haoqunjiang]

Okay…
Then we can make it a warning rather than an error for unknown package manager.

[zyy7259]

How about use an env variable to specify the bin used by PackageManager

[haoqunjiang]

Not necessary.
See the above snippets. We have 3 ways to determine the package manager to use, in the following order:

1. the command line --packageManager option
2. infer the command from the lockfile name in the project
3. the packageManager field in ~/.vuerc

The problem of custom package manager is not how to specify it, but how to map the subcommands:

vue-cli/packages/@vue/cli/lib/util/ProjectPackageManager.js

Lines 33 to 52 in a42f838

	const PACKAGE_MANAGER_CONFIG = {
	npm: {
	install: ['install', '--loglevel', 'error'],
	add: ['install', '--loglevel', 'error'],
	upgrade: ['update', '--loglevel', 'error'],
	remove: ['uninstall', '--loglevel', 'error']
	},
	pnpm: {
	install: ['install', '--loglevel', 'error', '--shamefully-flatten'],
	add: ['install', '--loglevel', 'error', '--shamefully-flatten'],
	upgrade: ['update', '--loglevel', 'error'],
	remove: ['uninstall', '--loglevel', 'error']
	},
	yarn: {
	install: [],
	add: ['add'],
	upgrade: ['upgrade'],
	remove: ['remove']
	}
	}

So if we want to support such a feature, we need to turn this error into a warning and then use the npm subcommands as fallbacks.

vue-cli/packages/@vue/cli/lib/util/ProjectPackageManager.js

Lines 78 to 81 in a42f838

	if (!SUPPORTED_PACKAGE_MANAGERS.includes(this.bin)) {
	throw new Error(`Unknown package manager: ${this.bin}`)
	}
	}

[zyy7259]

How about this #4621