Full support to pnpm and more

[rentalhost]

Added full support for pnpm, together with the already supported npm. Currently there is no support for yarn, but I believe this could be done at some point.

New features:

• Full support for the package manager pnpm;
• Support for monorepos and multiple workspaces (previously only the first folder in the workspace was supported, and the others presented conflicting results, as they used the first folder as reference). This is a new feature and at the same time a bug fix;
• Improvement in the file watcher of lock files:
  • Include support to watch pnpm-lock.yaml and the own package.json;
  • Watch files when updated, created or deleted, possibly resolving issue Plugin stuck on "Ready-to-install package ... Just run your package manager install command." #20.
• Include support to peerDependencies;
• Code intelligence for the extension to be "soft-disabled" if it is not possible to detect the presence of the npm or pnpm command (which is unlikely, but may happen);
• Using pnpm as the package manager for the extension from now on;
• Post-optimization of code using swc, which reduces the size of the compiled extension (vsix file) by about 3.6%, despite the new features.
• Updated code style and using most updated dependencies;

Big problem:

Unfortunately, I was not able to adapt to using ESM as the latest version of the extension. I don't know what to do. So since I'm more adapted to the "old way" and to be able to work quickly on these features, I decided to step back and base it on what I already know.

I don't know if it will be possible to continue with this PR like this.

[rentalhost]

@mskelton Did you think possible approves this PR? If the mentioned changes, especially regarding the ESM, are not in line with the project's current momentum, I will respect it. I just wanted your answer, as I share the extension with others, it would be nice to use it directly from the vscode repository. If it's not feasible for you, I would like to create a separate extension as a continuation of this one (although I really prefer to keep this one).

[wycats]

@rentalhost maybe create a temporary extension that highlights pnpm support and deprecate it as soon as it's merged.

The problems fixed here have been driving me nuts for weeks and I'd have loved to have found a fix earlier.

[rentalhost]

@wycats I have published now as npm-outdated plus.

[paul-uz]

Paging Dr @mskelton

[mskelton]

Hey all, sorry for the late reply. I've kind of been ignoring this repo since there has been a lot of good activity, but it hasn't be super relevant in my day to day. Glad to see you pushing the project forward.

@rentalhost To your questions, I'd say guide this project however you see best. If ESM is causing issues, feel free to drop it. I migrated most of my projects just for standardization, but if that's not the best for this, totally fine.

[wycats]

@mskelton maybe make @rentalhost a maintainer so they can push this forward?

[mskelton]

@wycats He already is a collaborator on the repo.