Katie Gengler

I think this is a version of this issue https://github.com/typed-ember/ember-cli-typescript/issues/780 Maybe @NullVoxPopuli would have more workarounds?

You can customize the options passed to yarn with the `buildManagerOptions()` function in the config https://github.com/ember-cli/ember-try/blob/master/README.md#config However, I think it is worth noting that `ember-cli` also does not support yarn...

I'd be happy to look at a PR, but, in general, yarn support in ember-cli and associated addons is somewhat stale. I opened this issue myself https://github.com/ember-cli/ember-cli/issues/10339 but have since...

I'm happy to look at a PR to support, but until then, the `buildManagerOptions` above is a decent workaround.

This is a bit outside the scope of ember-try. ember-try runs a command (by default `ember test`) with each scenario of dependencies specified. It technically doesn't know anything about the...

Ah, I thought you wanted the test command to fail as soon as it encountered a failure, which would be up to QUnit/Testem. I'll have to admit I'm still confused...

That seems correct to me. Here's the minimal docs: https://github.com/ember-cli/ember-try#ember-tryember-semver-string I believe it's trying for the previous two LTSes (based on 4 releases -- it wouldn't know about 2.18). It's...

I'm curious on why 2.12.2 is included and about the duplicate. The documentation for how the range works is in the readme under `versionCompatibility` (which is an old feature). I...

I don't think it is worth changing the behavior of the `ember try: ember` command. As you say, it is hardly used (other than by emberobserver which does rely upon...

The point of `ember try:ember` was to have something "smart" to test against ember versions in any project without necessarily having to have the config from the blueprint, so `ember-try-config`...