David Michon

I would normally expect warnings about package versioning to occur while running package manager operations, e.g. to warn during `install`, rather than at runtime. In other words "hey, you just...

Those aren't the same dependency; they have different peer dependency versions. Everything after the `_` is the description of the peer dependency configuration. For a single peer dependency it is...

An `@types/` `devDependency` may have zero impact at runtime, but it has a noticeable impact if you are compiling a TypeScript project against it, and pnpm has no way to...

I'm not seeing anything in your issue that explains why the rushstack repository is relevant. Looks like you should be filing this issue on rollup? https://github.com/rollup/rollup

Ah, ok, that makes more sense. From a closer look at that message, the issue is with the default helper emitted by TypeScript being incompatible with the ESM transformation that...

Which version of `@microsoft/load-themed-styles` are you using? The fix is in major version 2, since it was a breaking change to switch compilation target from ES5 to ES2017. You may...

The workaround you are using is, in fact, safe in practice, except insofar as the added latency allows more opportunities for merge conflicts in your branch. We'd accept a PR...

Verify that this file exists? `/Users/test/dev/test/common/temp/pnpm-local/node_modules/.bin/pnpm` If not, may need to use `rush purge` to clean up and then try again.

I'm not entirely happy with how the opt-in currently works. I expect it may be best to have an express option in the moduleKindsToEmit collection to emit the shim.

The `@rushstack/ts-command-line` library doesn't currently support this concept, so this capability would need to be added there. The linked PR is a different concept altogether, namely running other code in...