Fixes and improvements

[CGNonofr]

implements #190
fixes #198
fixes #199
workaround for #113

released as 1.82.4-next.1

[kaisalmen]

@CGNonofr changes looks good, but I see one problem with @codingame/monaco-editor-treemended. If I import it as such:

"monaco-editor": "npm:@codingame/monaco-editor-treemended@>=1.82.4-next.1 <1.83.0"

then it will conflict/be incompatible with the regular monaco-editor version (e.g. 0.43.0) people have in their dependency tree.
Any idea how to solve this? Is it possible map the imported version to another one like we basically do it with the name?

[CGNonofr]

@CGNonofr changes looks good, but I see one problem with @codingame/monaco-editor-treemended. If I import it as such:

"monaco-editor": "npm:@codingame/monaco-editor-treemended@>=1.82.4-next.1 <1.83.0"

then it will conflict/be incompatible with the regular monaco-editor version (e.g. 0.43.0) people have in their dependency tree. Any idea how to solve this? Is it possible map the imported version to another one like we basically do it with the name?

What about using the npm overrides feature?

[kaisalmen]

What about using the npm overrides feature?

Didn't know this one. Question is if this introduces more problem then it solves regarding treemending and yarn, pnpm, etc

[kaisalmen]

LGTM. My question regarding version conflicts does not block the approval.

[CGNonofr]

What about using the npm overrides feature?

Didn't know this one. Question is if this introduces more problem then it solves regarding treemending and yarn, pnpm, etc

That solution is not perfect either, but it's an alternative to the treemending. It's probably easier for pnpm