Update NPM dependencies to latest (OSOE-954)

[Piedone]

The project's NPM dependencies are outdated, and Renovate updated them. But, due to breaking changes, manual fixes are necessary; if you update all packages even to at most minor versions, you'll be greeted with the following warnings and errors in VS, necessitating fixes in other projects too:

• Open an issue branch from the branch of Update All packages #114 and once you're done with that, merge the branch of Update All packages (major) #115 too.
• Check all updated dependencies: Are they actually all needed?
• Fix any compatibility issues, including in other OSOCE projects, like the Base Theme as seen in the above screenshot.
  • To fix any "require() of ES Module ... not supported" type error, you can use await import() inside an asynchronous method, like here.
  • When upgrading ESLint to the latest v9.x then configurations have to be migrated, see here.
  • When upgrading StyleLint "The CommonJS Node.js API is deprecated."
• Should we pin the PNPM version in every project's "packageManager" property? It seems like a safe way to take dependency on a given PNPM version, which can also be auto-updated by Renovate. If indeed, then corepack prepare pnpm can be removed from NodeJsExtensionsNpmPackage.targets, the enable-corepack action, and documented (and ideally automatically enforced somehow) that this property should be always added.
• Remove the temporary "All packages" group from renovate.json5 here and "ESLint" group from Lombiq.VueJs.

After merging the issue branch, both renovate PRs should close itself.

Jira issue

[Piedone]

Maybe you're interested, @sarahelsaig @dministro?

[Piedone]

@sarahelsaig @dministro?

[Piedone]

Related: Lombiq/Open-Source-Orchard-Core-Extensions#965

[dministro]

It makes sense to do them together. I can take them once I finish the remaining tasks under UITT.

[Piedone]

I suppose so. If not, this should be done first.

That would be awesome!

[sarahelsaig]

I might be able to do this later this week.

Also I have an idea that would remove the need to add ESLint dependencies to projects using NE. That's somewhat related to this issue since we'll have to update ESLint config loading here anyway. Is it okay to try it in this issue, or should I open a separate one?

[Piedone]

Yeah, please do it here.

We bumped into the ESLint dependency being necessary or not in projects using NE. The result was that when used from a submodule, you don't need to ESLint to the consuming projects's packages.json, but when used from NuGet you have. See https://github.com/Lombiq/DotNest-Core-Sites-SDK/pull/102#issuecomment-2816821021 and the related submodules PRs where similarly the ESLint dependency removal is reverted, like Lombiq/Show-Orchard-Theme#25.

This is less than ideal, of course, and if we can do it better we should.

[Piedone]

How does this change now that corepack will be removed from the default Node installation?

[Piedone]

PNPM can now also manage itself: https://github.com/pnpm/pnpm/releases/tag/v9.7.0.