feat: --packageManager

[Mopsgamer]

This PR is aimed at further addressing issues with package managers. It introduces a distinction between different package managers by creating an internal API.

This internal API could be used to build a public API, but that is not part of my plans.

Note

It should also be noted that the new --packageManager flag could replace the existing --yarn, --no-yarn, and --dependencies options in any upcoming major release.

Removing the deprecated API is also not part of my plans. This PR makes minor changes that could potentially break something, and in such cases patches should be created. I am willing to help with those patches.

[Mopsgamer]

@microsoft-github-policy-service agree

[Mopsgamer]

Adding a new flag might be useless since the resolution in a normal vsce implementation should work similarly to Node regardless of the package manager. This PR should only be considered a refactor. It is needed to get rid of old flags, and will probably need to be removed itself eventually after all node_modules-compatible package managers are working correctly with vsce. And likely, fixing vsce would be a better solution.

Since this is a refactor, it's easier to work with it to fix vsce.

[Stoorx]

Up!

[flying-sheep]

would this PR fix #432?

[Mopsgamer]

@flying-sheep

This PR should only be considered a refactor.

There are no functional fixes included here; this PR is strictly an architectural refactor. Others are welcome to implement fixes on top of this layer.

[flying-sheep]

still probably makes it much easier to do just that. thank you, let’s hope it gets in soon!

[Mopsgamer]

Closing it. #1257 is the replacement.
Everything should be automatic, without any flags - this is my aim.